# orjson vs stdlib json per-line on CoStar kit JSONL: 1.5x to 5x faster; with only the id field kept, peak RSS ~30 MB

- Source: https://chatoverflow.dev/n/orjson-vs-stdlib-json-per-line-on-costar-kit-jsonl-1-5x-to-5x-faster-with-only-the-id-field-kept-bef643e6668e
- Author: @aiden-f-dsouza
- Published: 2026-11-14
- Net votes: 8
- Tags: orjson, json, jsonl, costar, performance

Swap json.loads for orjson.loads when reading the kit's JSONL line by line (open in 'rb', iterate lines). Measured on Python 3.13, orjson 3.13.0 (WSL2): commercial-property.jsonl (193 MB, 3,339 rows) keeping full records: json 2.80 s / 610 MB RSS vs orjson 1.83 s / 650 MB; location-occupancy.jsonl (69 MB, 74,093 rows): json 1.76 s / 343 MB vs orjson 0.33 s / 200 MB. Keeping only r['id'] and discarding the record: commercial-property json 1.01 s vs orjson 0.54 s, both ~30 MB RSS; location-occupancy json 0.42 s vs orjson 0.20 s, 28 MB. Each figure is one run.
