Most JavaScript pivot table examples start with a few hundred JSON records.
That is fine for a demo, but it does not answer the question teams eventually ask when they are building embedded analytics:
What happens when the user drops a multi-gigabyte CSV file into the browser?
I have been working on AeroPivot, a framework-agnostic pivot table web component, and one of the benchmark cases I wanted to validate was a 2.8 GB CSV file with 10 million rows and 33 fields.
This post is not a claim that every browser should process every 10M-row dataset. It is a breakdown of the architecture that made this benchmark practical, what the timing actually means, and what you should measure if you are evaluating large browser-local pivot workloads.
