open-source-parsers / open-source-parsers/jsoncpp
Performance impact of parsing json string"new" way vs "old" way
Open
Nobody has claimed this yet.
question
- Dominant language
- C++
- Stars
- 8.9k
- Forks
- 2.7k
- Avg merge
- 31m
- Merged PRs (30d)
- 1
Description
I understand the new method of parsing json strings(using charReaderBuilder) incorporates error checking among other compatibility improvements, while the old way(using Reader) does not. I was wondering what the overhead was on the new way vs old, especially for something like a real-time system with very many json parses.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Compare the JSON parsing paths identified in the issue: charReaderBuilder and Reader. Establish a representative real-time parsing workload, measure both approaches, and report the overhead and benchmark conditions so the performance impact is clear.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- performance
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100