Export to CSV making page unresponsive when records are large
Export to CSV making page unresponsive when records are large
rachitS
Posts: 2Questions: 1Answers: 0
Can anyone please suggest that when using CSV export option for records greater than ~65000 approx why the page becomes unresponsive? Is there any functionality present which can add new sheet when records are greater or do I need to implement it on my own?
This discussion has been closed.
Answers
For large tables you should probably consider having the CSV files server-side generated and then downloaded. Having said that, 65000 rows should probably be okay. Can you link to the page so I can performance trace it please?
Allan
Hey Allan. Thanks for responding. Sorry I cannot share the page because of some security concerns. In my case there can be a scenario where records in table exceeds 65k .
Shouldn't I use datatable CSV export?
I have given functionality to operations team such that on web app they can execute a select query and download results to csv. Now there can be some cases where users wishes to export all data( can be million records as well). I am presently using CSV export.
Now please suggest me should I go with this approach (using jquery plugin) or should I change the approach and make that export using aspose/open xml or with epplus on server side.
Thanks
Without a test case to run a performance trace on, I can't really say for sure if there is a problem in the export that is slow (certainly older versions of the software have run a lot slower than the new ones now are as I've been able to improve the performance somewhat).
If the Buttons extensions isn't running fast enough, it might be that you are running into a client-side processing limit and you would need to generate the file server-side as I said above. But really I'd need to be able to test it to understand fully.
Allan