Open saravan23 opened 7 years ago
This is being tracked here as well https://datatables.net/forums/discussion/39534/
The default compression is STORE
, meaning no compression of the content. Switching to DEFLATE
should reduce the final size.
1 minute to generate a 54MB zip file seems a bit long. I suspect the use of binary strings or base64 somewhere. Which output format do you use ? blob
? base64
?
Thank you for the response. I'm using v3.1.3 of JSZip. After changing to DEFLATE, apparently the size came down to 5.5 MB which is ~10 times lesser than the original size. However, in IE 11 and Edge browsers, still the file is not even opening.
Any other pointers on this to make this work in IE11/Edge browsers?
Here's demonstration link (http://live.datatables.net/najokiwa/1/edit) of the issue. you may please try this in IE11/Edge browsers. For testing purpose, I've cut down the data to 15k records. However, this is still failing.
The output format we're using is blob.
Thanks for the link. I don't have a lot of time to investigate right now, I'll try to do it this week or next week. What's the behavior in IE11/Edge ? Silently stopping ? Does the promise fail with an error ?
In IE/Edge, For 15k records while exporting - its taking around 7 to 8 minutes. However, this is really faster in chrome [which is taking around 5 to 6 seconds].
Any clues/thoughts on improving the performance on IE/Edge browsers while exporting excel of the large data sets?
After a quick profiling of the page on Edge, it seems a lot of time is spent doing string operations (strip
in dataTables.buttons.js
) or manipulating a DOM (_createNode
in buttons.html5.js
). This is outside of JSZip so I can't really comment on this part. I also don't know my profiling is relevant: I used the Edge VM on a linux laptop and everything was quite slow (and may not represent a real Edge installation).