Benchmark and improve object creation
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 693
- Forks
- 49
- PR merge metrics
- No merged PRs in 30d
Description
Benchmarks of https://github.com/iboB/huse show unexpectedly long time spent in object creation where the type cache query is practically a hit 100% of the time. It seems that it takes 90us to create an object in the json-parse benchmark there.
We should benchmark (and likely optimize) object creation.
- Check with a known type:
mutate_to - Check by mutating to a hit:
mutateleading to a known type
Contributor guide
No contributing guide indexed for this repository
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
Start by running the json-parse benchmark from the linked huse project and inspect object creation through the named mutate_to and mutate paths. Compare creation for a known type with mutation to a cache hit; done means the benchmark identifies the cost and the optimized implementation shows an improvement without changing behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- performance
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100