NibiruChain / NibiruChain/nibiru
feat(simulations): add statistic of chain usage and performance for simulation change
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 206
- Forks
- 232
- Avg merge
- 1d 17h
- Merged PRs (30d)
- 18
Description
When a PR updates any of the simulation workflow, we need to understand the impact for several metrics:
- Average block size
- Average gas consumed by transactions (per type?)
- other metrics??
This way we can have an idea of the delta introduced by each new transactions or changes in begin block / end block.
it would be awesome to have some automatic report when creating the PR and running the tests!
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 locating the simulation workflow and the tests it runs. Clarify which metrics are required beyond average block size and average gas consumed by transaction type, then determine how an automatic report should be produced when a pull request runs the tests. Done means the agreed metrics and reporting behavior are defined and implemented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- blockchain, performance, testing
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100