lambdaclass / lambdaclass/lambda_ethereum_consensus
Check atom count on long-running node
Open
Nobody has claimed this yet.
bug
needs elaboration
P3
- Dominant language
- Elixir
- Stars
- 109
- Forks
- 41
- PR merge metrics
- No merged PRs in 30d
Description
Running the node resulted in the following graph on the unique atom counts. We should keep in mind this behavior and check if it's a one-time thing or if it's continuous (then we should fix it ASAP).
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
No file, test, or entry point is named. Start by reproducing the long-running node and measuring the unique atom count over time; determine whether the graph is a one-time event or continuous growth, with the issue resolved when the behavior is characterized and any continuous growth is fixed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- elixir
- Domain
- performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100