hiero-ledger / hiero-ledger/hiero-consensus-node

Performance test catching up BN's at high TPS (entire block buffer)

Open
#25,008 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
Java
Stars
406
Forks
226
Avg merge
3d 4h
Merged PRs (30d)
210

Description

### Background

A test to do is check how the BN handles potentially streaming dozens of blocks that are large. e.g. at 10K TPS, if all those blocks are buffered and then we suddenly get a connection to a BN, can the BN handle a large volume of traffic across multiple blocks/requests in a very short time.

### Acceptance Criteria

TBD

### Dependencies

_No response_

### Definition of Ready (DoR) Checklist

- [ ] Clear acceptance criteria
- [ ] Clear and detailed description
- [ ] Dependencies identified
- [ ] Links to documentation
- [ ] Should be completable in 2-3 Days
- [ ] Initial draft of Low-level design document
- [ ] At least high level test plan
- [ ] Groomed/Estimated

### Definition of Done (DoD) Checklist

- [ ] Acceptance Criteria complete
- [ ] No Codacy issues greater than minor (in new code)
- [ ] JavaDocs updated/created
- [ ] Code commented
- [ ] Unit tests created/updated
- [ ] 80% test code coverage (in new code)
- [ ] Happy Path and major negative cases in HAPI tests as applicable

Contributor guide

Open the contributing guide

Research direction

No files, tests, or entry points are named. Start by locating the BN block-buffering code and existing performance-test harness, then establish a test plan for dozens of large blocks at 10K TPS and a burst of multi-block requests. Done requires agreed acceptance criteria and evidence that the BN handles the defined traffic volume.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
performance, testing
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.