hiero-ledger / hiero-ledger/hiero-consensus-node
Inefficient (CPU-intense) version checking
Open
Nobody has claimed this yet.
Scalability
- Dominant language
- Java
- Stars
- 407
- Forks
- 226
- Avg merge
- 3d 4h
- Merged PRs (30d)
- 210
Description
Description
It was performance-triaged as a bug - unnecessary very intense version checking: https://perf.analytics.eng.hashgraph.io/permanent/engnet2-20240906_175600/reports/com.swirlds.state.spi.HapiUtils.html#35
Steps to reproduce
TOM's or Oleg's 20 mins test
Additional context
No response
Hedera network
No response
Version
v0.54
Operating system
None
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
The linked performance report points to com.swirlds.state.spi.HapiUtils; start there and reproduce the referenced 20-minute TOM/Oleg test. Trace the version-checking path and use the same performance report or test to confirm that unnecessary CPU-intensive checks are eliminated.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100