NXS vs JSON vs CSV — Browser Benchmark

The same fixtures used in the Node and Go benches, run in your browser over fetch().

Ready.

1. Open file — parse the entire structure

JSON and CSV eagerly parse every byte; NXS reads only the header + tail-index.

2. Random-access read — one field from record k

Once data is in memory, read record[k].username. Measures warm property access.

3. Random-access read — multiple fields from record k

Read 4 fields per random record (username, age, balance, active). NXS amortises header parsing after the first field.

4. Cold pipeline — fetch + parse + one field

The realistic browser scenario: user hits page, data fetched, first field read.

5. Aggregate — sum of 'score' across all records

Uses format-specific optimisations: JSON.parse + loop, raw CSV column scan, NXS bulk reducer (WASM if loaded).