go-ethereum icon indicating copy to clipboard operation
go-ethereum copied to clipboard

Questions about running an archive node

Open fortuna502 opened this issue 7 months ago • 5 comments

Hello Geth Team,

I am setting up an archive node using Geth and would appreciate guidance on the following aspects:

  1. Benchmark Tests and Performance Metrics:
  • Are there any official or community-shared benchmark tests for running an archive node with Geth?
  • Specifically, what is the typical Queries Per Second (QPS) for RPC methods like eth_call on an archive node? If there are no standard metrics, could you point me to resources or methods for benchmarking this myself?
  1. Syncing an Archive Node:
  • Does running an archive node with Geth require syncing from block 0 (genesis block)? Or can it start from a more recent block while still maintaining full historical state?
  • How long does the initial sync typically take for an archive node, assuming standard hardware (e.g., 16-core CPU, 64GB RAM, and high-performance SSD)?
  • Are there any recommended sync modes or flags (e.g., --syncmode full) for optimizing the sync process?
  1. Archive Snapshots:
  • Does Geth provide any pre-synced archive snapshots that can be used to speed up the initial setup of an archive node?
  • If not, are there third-party services or community resources that offer such snapshots for Geth?

Thank you for your assistance. I look forward to your insights and recommendations.

fortuna502 avatar Apr 21 '25 04:04 fortuna502