-
Notifications
You must be signed in to change notification settings - Fork 251
Open
Labels
Description
Problem to solve
After running benchmarks on dedicated hardware, we need a publishable document consolidating the results across all workload scenarios.
Proposed solution or feature
Write a benchmark document that includes:
- hardware specs, software versions, configuration
- per-workload results table (MGas/s, TPS, block intervals, ev-node overhead)
- latency breakdown from trace spans
- identified bottlenecks and optimization opportunities
Alternatives considered
N/A
Additional context
Part of #2288. Depends on throughput experiments completing on dedicated hardware.
A sample of what this could look like based off WIP data
## ev-node Benchmark Results
| Metric | ERC20 | GasBurner |
|---------------------|------------|------------|
| MGas/s | 55.14 | 458.00 |
| TPS | 1414 | 153 |
| s/Ggas | — | 2.18 |
| Block interval p50 | 102ms | 108ms |
| Block interval p99 | 245ms | 312ms |
| Gas/block avg | 12.3M | 2.6G |
| Non-empty ratio | 19.8% | 100% |
| ev-node overhead | 1.6% | 2.1% |
### Latency Breakdown (avg μs)
| Span | ERC20 | GasBurner |
|-----------------------------|--------|-----------|
| BlockExecutor.ProduceBlock | 116000 | 85000 |
| Executor.ExecuteTxs | 114000 | 83000 |
| Engine.GetPayload | 1200 | 1100 |
| Engine.NewPayload | 2400 | 2200 |
| DA.Submit | 50 | 48 |
**Config**: ev-node@abc123, ev-reth@pr-140, 100ms block time, 50M gas limit
**Hardware**: <machine spec>
**Date**: 2026-03-03Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
Type
Projects
Status
No status