Optimize elemental.json
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 1.8k
- Forks
- 717
- Avg merge
- 2d 6h
- Merged PRs (30d)
- 3
Description
Originally by @Legioth
Benchmarking done in #14666 shows that elemental.json is significantly slower than org.json. Initial analysis shows that the implementation of toJson() makes up a significant amount of the time spent in json library code, and there's also lots to be gained from a more straightforward implementation of that functionality.
Imported from https://dev.vaadin.com/ issue #15394
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
Start by reviewing benchmark #14666 and the elemental.json implementation of toJson(), which the issue identifies as a significant source of library runtime. Compare the current behavior and timings with org.json, then use the benchmark results to confirm that the revised implementation improves serialization performance without changing output.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- performance
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100