1 points | by StellaMary 12 hours ago ago
3 comments
Parsing .xlsx in JS with libraries like SheetJS often means:
Loading the whole 100 MB file into memory Blocking the main thread Tabs freezing, fans spinning xlsx-lite does it differently:
Streams ZIP entries (no inflate-to-Vec) Async + cooperative yielding — browser paints while parsing Batch-based parsing (rows in chunks) Memory stays flat, UI stays responsive
For reference, my test case: a 40MB XLSX with ~200k rows.
Parsing with this WASM build: ~16ms (on Chrome, M1 Mac).
Parsing with JS (SheetJS): seconds, often >5s, with UI stutter. So the speed difference is very noticeable on big files.
Curious if anyone here has even larger datasets to try!
Give a try and share your feed back..!! Will be sharing for react and vue ASAP.
Parsing .xlsx in JS with libraries like SheetJS often means:
Loading the whole 100 MB file into memory Blocking the main thread Tabs freezing, fans spinning xlsx-lite does it differently:
Streams ZIP entries (no inflate-to-Vec) Async + cooperative yielding — browser paints while parsing Batch-based parsing (rows in chunks) Memory stays flat, UI stays responsive
For reference, my test case: a 40MB XLSX with ~200k rows.
Parsing with this WASM build: ~16ms (on Chrome, M1 Mac).
Parsing with JS (SheetJS): seconds, often >5s, with UI stutter. So the speed difference is very noticeable on big files.
Curious if anyone here has even larger datasets to try!
Give a try and share your feed back..!! Will be sharing for react and vue ASAP.