NethermindEth / NethermindEth/json-bench
high level plan for json-bench
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 1
- Forks
- 2
- Avg merge
- 10h 35m
- Merged PRs (30d)
- 10
Description
- Ensure basic happy path works as described in readme
- Make sure the data is sent to the database and is readable via grafana (currently i only tested the local RPC dashboard)
- Ensure reading RPC calls from disk and submitting to node + collecting info works as a workflow
- Move over all existing JSON-RPC tests into this folder (or use git submodule)
- Check if the metrics exposed and collected by k6 is enough, for e.g do we collect p99 for every call or just for all calls together?
- Expand the list of calls and scenarios by talking to Quicknode, Alchemy (existing doc from geth team can be used as starting point), etc (Pari and Kamil help here)
- Run against bloatnet shadowfork (in kurtosis set
network: perf-devnet-2-shadowforkand it'll automatically create a local shadowfork
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 with the README, the local RPC dashboard workflow, and the existing JSON-RPC tests mentioned in the checklist. Then inspect how data reaches the database and Grafana, how RPC calls are read from disk and submitted, and how k6 metrics are collected. Done means the listed workflows, tests, metrics, scenarios, and bloatnet shadowfork run are covered.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, grafana
- Domain
- observability, performance, testing-qa
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100