Closed lemire closed 4 years ago
Maybe in HPS (Handle-per Second)
or PPS (Parse-per-Second)
?
@dalisoft The original repo already does GB/s. Also it's how we usually evaluate streaming/text processing on papers, that is why he mentions GB/s.
Would be nice to see benchmark, i know only Request/sec or calls per second. About GB/sec i see, but never realized in benchmarks
You have to define the payload for requests per second to be meaningful. Parsing an empty JSON document can be done an infinite number of times per second.
@lemire Yes, i understand. 3-4 types of JSON payloads.
{ "status": "success" }
- One-line simple responses{ "status": "success", "data": { "id": "uuiv4", ...other_datas } }
- User-data or simple query responses (max 1Kb){ ...type2, "ref": { ...$ref_data, ...data_too_here } }
- Structured data of users with their references (~3-4K)I can benchmark with these type of datas if necessary
@dalisoft
If the document is small enough, we reach millions of documents parsed per second. This was tested upstream. Our benchmarking tools now report the number of documents parsed per second.
PR #33 closes this issue
It would be more interesting if we could report the timings (in the README.md) in GB/s, or some other normalized metric.