NethermindEth / NethermindEth/state-benchmarks

[META] Mainnet 10x bloated state benchmarks

Open
#1 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Blocked
Dominant language
Python
Stars
0
Forks
0
PR merge metrics
No merged PRs in 30d

Description

flowchart TB

%% -----------------------
%% PHASE 1 – PREPARATION
%% -----------------------

subgraph Preparation
A[Review previous Bloatnet work]
B[Select baseline mainnet snapshot]
C[Establish metrics for DB size and structure]
D[Collect data about detailed mainnet structure]
end

A --> C
B --> D
C --> D

%% -----------------------
%% PHASE 2 – BLOATING TOOLING
%% -----------------------

subgraph Bloating Tooling
E[Implement efficient bloating method]
F[Prepare a set of transactions for bloating]
G[Collect new payloads for bloating]
end

D --> F
E --> G
F --> G

%% -----------------------
%% PHASE 3 – STATE GENERATION PIPELINE
%% -----------------------

subgraph State Generation
H[Generate 1.5x mainnet bloated state]
I[Test snap sync on 1.5x state]

J[Generate 2x mainnet bloated state]
K[Test snap sync on 2x state]

L[Generate 3x mainnet bloated state]
M[Test snap sync on 3x state]

N[Generate 5x mainnet bloated state]
O[Test snap sync on 5x state]

P[Generate 7x mainnet bloated state]
Q[Test snap sync on 7x state]

R[Generate 10x mainnet bloated state]
S[Test snap sync on 10x state]
end

G --> H
H --> I
I --> J
J --> K
K --> L
L --> M
M --> N
N --> O
O --> P
P --> Q
Q --> R
R --> S

%% -----------------------
%% PHASE 4 – TESTING & REPORT
%% -----------------------

subgraph Testing
T[Write new stateful tests]
U[Run benchmarks on every state size]
V[Write final report]
end

A --> T
I --> U
K --> U
M --> U
O --> U
Q --> U
S --> U

T --> U
U --> V

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No files, tests, or entry points are named. Start by reviewing previous Bloatnet work, selecting a baseline mainnet snapshot, and defining database-size and structure metrics. Done means generating 1.5x through 10x states, testing snap sync at each size, running the benchmarks, and writing the final report.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
blockchain, database, performance, testing-qa
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.