JanusGraph / JanusGraph/janusgraph
Use Vanilla Java instead of Stream API for performance critical sections
- Dominant language
- Java
- Stars
- 5.8k
- Forks
- 1.2k
- Avg merge
- 13h 53m
- Merged PRs (30d)
- 6
Description
As benchmarked by @mad (https://github.com/JanusGraph/janusgraph/pull/2098#discussion_r415074443) and @rngcntr (https://github.com/JanusGraph/janusgraph/pull/2105#discussion_r419973555) Vanilla Java has better performance characteristics then Stream API.
Thus, I am suggesting to use Vanilla Java code in performance critical sections.
Contributor guide
Research direction
Start with the benchmark evidence in PR 2098 discussion_r415074443 and PR 2105 discussion_r419973555, then locate the performance-critical sections using the Stream API. The issue does not name files, entry points, or benchmarks, so the scope and completion criteria need to be established before work begins.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- performance
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100