Read the full article: https://dev.to/q9/ethereum-2-0-mainnet-clients-3and (mirror)
- Machine: Hetzner Dedicated Root Server EX42-NVMe
- Location: HEL1 (Helsinki, Finland)
- OS: Arch Linux latest minimal (English)
- CPU: Intel Core i7-6700 (QuadCore/Skylake/HT)
- RAM: 64GB DDR4
- Disk: 2x512GB NVMe SSD (RAID 1)
- Spec version:
v1.0.0 - Circa
420_000slots at start time - 5 different clients compatible with mainnet spec
-
Lighthouse v1.1.0-e4b6213 -
from git
tags/v1.1.0 -
Rust
1.49.0, Cargo1.49.0 -
Built in
--releasemodecargo build --release
-
beacon-chain version Prysm/v1.1.0/9b367b36fc12ecf565ad649209aa2b5bba8c7797. Built at: 2021-01-18 19:47:14+00:00 -
from binary release
v1.1.0./prysm.sh beacon-chain
-
teku/v21.1.1/linux-x86_64/oracle_openjdk-java-11 -
from git
tags/21.1.1 -
Java
11.0.10, Gradle6.8.1 -
Built in dist mode
./gradlew installDist
-
Nimbus beacon node v1.0.6-87955f2d-stateofus -
from git
tags/v1.0.6 -
Nim
1.2.6, Make4.3.0 -
Built in
-d:release -d:insecuremodeNIMFLAGS="-d:insecure -d:release" make -j $(nproc) nimbus_beacon_node
-
lodestar 0.14.0 -
from git
tags/v0.14.0 -
Node
12.20.1, Lerna3.22.1 -
Built in default mode
lerna bootstrap
unix: unix time of data in secondstime: time since client start in secondsslot: current client slot as numbersps: slots per second as reported by client in seconds^{-1} (lighthouse only)db: database size in bytespc: connected peer count as numberout: outgoing network traffic by beacon node process in bytes (vianethogs)inc: incoming network traffic by beacon node process in bytes (vianethogs)cpu: average%usercpu usage over last second of host system in percent (viampstat)- metrics derived:
vtime: adjusted time; 0 once first slot syncedsps60: 60s moving average fromslotnumber andtimevariablenout: regard out traffic as negative value-outtrff: sum ofincandout
- eth2-bench-2020-10 (Medalla Testnet)
- eth2-bench-2020-07 (Altona Testnet)
- eth2-bench-2020-06 (Witti Testnet)
See also: Resource Analysis of Ethereum 2.0 Clients (Barcelona Supercomputing Center)
