Blog

High-performance servers feeding blockchain data into an analytics dashboard

Scaling Blockchain Analytics & Indexing with Dedicated NVMe-Powered Servers

Blockchain analytics has reached terabyte scale, but node storage depends on the client and retained history. Geth’s path-based archive requires around 2 TB for full flat state history, or approximately 6.5 TB when historical trie data is retained for proofs. Those figures describe the node database: decoded events, secondary indexes, derived tables, and backfill workspace need additional capacity.

Choose Melbicom

— 1100+ ready-to-go servers

— 21 Tier III & IV data centers

— Up to 200 Gbps per server

Order a server

Engineer with server racks

High‑performance dedicated servers provide multi‑core CPUs, large RAM pools, and fast local NVMe for sustained node and indexing workloads. Melbicom offers single‑tenant configurations matched to ingestion and query needs.

Blockchain and Analytics

Blockchain analytics ETL flow from node data through decoding and normalization to analytical queries
From chain records to queryable analytics. Source: Blockchain Data Analytics.

A blockchain records on-chain activity: transfers, swaps, liquidations, governance votes, and NFT mints. Blockchain analytics is about turning those records into structured data that powers dashboards, risk models, and compliance workflows.

Analytics stacks commonly follow an ETL pattern:

  • Extract blocks, transactions, and logs from nodes across many chains, plus state diffs where the client exposes them.
  • Transform them into normalized tables (addresses, token transfers, positions, fees).
  • Load them into OLAP engines, column stores, or time‑series databases for aggregations.

A review of blockchain data analytics highlights scalability, data accessibility, and accuracy once datasets reach multi‑terabyte size. Add multi‑chain and multi‑year history, and you’re firmly in big‑data territory.

In practice, modern platforms resemble web‑scale analytics systems: parallel ETL workers feeding NVMe‑backed warehouses, with query engines distributing scans across many cores. The bottleneck stops being “can we parse this?” and becomes “can our infrastructure ingest and query on‑chain data fast enough?”

What Specs Improve Blockchain Indexing?

Blockchain indexing benefits from fast CPU cores, enough RAM for node caches and concurrent queries, and low-latency NVMe for active data. On dedicated servers, size these resources for the selected clients, retention window, and ETL workers; add network capacity for synchronization and API traffic.

Recommended RAM by node role for Ethereum and Solana Agave
Recommended node RAM, including Ethereum execution and consensus clients; add capacity for ETL and analytics. Source: EIP-7870 and Agave requirements.

CPU and Parallelism

Indexers can divide work by chain, contract family, or ETL stage. On a host consolidating many nodes and ETL workers, a 32‑ or 64‑core CPU supports substantial concurrency, while single‑thread speed still matters for replaying blocks and verifying signatures.

Melbicom offers high-core AMD EPYC options in Web3‑optimized builds for concurrent node and ETL workloads.

Memory and Caching

Memory is the first line of defense against slow storage. Node clients and indexers cache as much state as RAM allows so they don’t hit disk on every lookup.

Size RAM for the node clients and analytical working sets together. Ethereum’s hardware guidance recommends 32 GB for a full node and 64 GB for a validator. Agave requirements specify 256 GB+ for a Solana validator and 512 GB+ for RPC with all account indexes. Add ETL and query memory when sharing a host.

Storage, Network, and NVMe for Hot Data

Storage and network are where indexing pipelines either fly or stall. Multi-chain node databases and analytics warehouses compete for capacity and I/O. Storage latency matters for state access, while large analytical scans also depend on sustained throughput.

Use fast local NVMe for active node databases and write-heavy indexing. Erigon’s guidance emphasizes disk latency for block execution; a high sequential transfer rate alone does not establish indexing speed.

Size network capacity for concurrent synchronization, backfills, replication, and API traffic. For staked Agave validators, Anza recommends 10 Gbps of available bandwidth; other node roles can need less.

Melbicom offers ports up to 200 Gbps per server, with metered and unmetered plans for sustained transfers and analytics API traffic.

Dedicated, Single‑Tenant Environments

Dedicated servers isolate host CPU, memory, and local storage from other tenants. Running directly on the host avoids a hypervisor layer, making long-running node and ETL workloads easier to profile. Processes sharing that host still compete for its resources.

Table 1. Server Components That Actually Move the Needle

Component Role in Pipeline Why High‑End Specs Matter
CPU (Cores & GHz) Runs node clients, parsers, ETL workers More cores support concurrent workers; fast individual cores accelerate serial execution.
RAM Caches state and query working sets Large memory reduces disk hits during indexing and queries.
NVMe SSD Stores chain DBs and analytics datasets Low read latency supports state access; sustained throughput supports large scans.
Network Uplink Moves blocks in and query results out Uplink capacity supports concurrent synchronization, replication, and API traffic.
Single‑Tenant Dedicated Hardware Provides isolated, predictable resources Dedicated host resources avoid contention from other tenants.

NVMe Configuration for On-Chain Analytics

For on-chain analytics, use local NVMe for active node databases and write-heavy tables, separating those paths when they compete for I/O. Choose drives by sustained-write performance, latency, and endurance. Keep cold history and snapshots on a separate storage tier so capacity growth does not crowd out the active working set.

Multiple NVMe Drives for Parallel I/O

Analytics workloads are highly parallel: workers scan different partitions while nodes append new blocks and ETL jobs compact or re‑index tables. Separate physical NVMe drives can reduce contention between these paths. RAID0 stripes data without redundancy: one drive failure loses the array. Use it for rebuildable data or replicas when recovery time is acceptable; use mirroring when local drive-failure protection is required.

A practical layout for an Ethereum-focused node-and-analytics host:

  • NVMe 0: chain database
  • NVMe 1: analytics warehouse (columnar or time‑series DB)
  • NVMe 2: ETL scratch space and logs

This separation reduces competition for disk I/O between analytical queries and node updates. For Solana RPC nodes, keep accounts and ledger on separate drives.

Enterprise NVMe Over Consumer Shortcuts

Under indexing loads, you’re writing and rewriting terabytes. For active node databases and sustained ETL writes, prefer enterprise-grade TLC NVMe with DRAM and an endurance rating matched to the expected write volume. Check sustained-write performance rather than relying only on peak IOPS.

Ethereum’s hardware guidance discourages DRAM-less and QLC drives for node workloads. Enterprise QLC can suit read-heavy storage, so select flash for each tier’s access pattern.

Local NVMe Plus Object Storage for Cold Data

Not every byte needs NVMe forever. Historical partitions older than a certain horizon may see limited traffic outside audits and backtesting.

A pragmatic design is:

  • Keep the active window (recent blocks and hot tables) on local NVMe.
  • Export older partitions and periodic snapshots to S3‑compatible object storage.

Use the database’s supported object-storage tier or export format for historical partitions; moving live node database files to a bucket is not a substitute for local storage. Melbicom’s S3-compatible storage accepts these datasets and snapshots with free ingress.

DefiLlama and Blockchain Analytics

DefiLlama turns blockchain data into comparable DeFi metrics such as total value locked, fees, and trading volume. Most of its TVL adapters retrieve data through direct on-chain calls; some use subgraphs or APIs. For comparable analytics services, reliable ingestion and consistent methodology matter alongside the hardware serving queries.

DeFi analytics dashboard showing total value locked and protocol metrics across blockchain data sources

The Graph’s subgraphs provide another route to structured data by mapping selected contracts and events into entities queried through GraphQL. Using a suitable existing subgraph can reduce the indexing a team operates, while direct node access supports workloads that need other state or history.

Teams building similar multi-chain views should size ingestion, historical retention, and query concurrency separately. Full and archival nodes supply chain data; indexers turn it into structured records, and analytics engines serve user queries. These workload boundaries determine where additional CPU, RAM, or NVMe capacity is useful.

Scaling Blockchain Analytics

Scaling blockchain analytics with Melbicom

High-performance dedicated servers are a practical choice for sustained blockchain analytics workloads that need dedicated CPU, memory, and local storage. Size the platform for the chains you actually index, the history you retain, and the queries you serve.

For teams designing or scaling analytics pipelines, a few principles stand out:

  • Design for multi‑chain growth. Plan capacity around the selected chains, retained history, and concurrent queries.
  • Keep hot data on NVMe. Separate competing I/O paths and keep cold data on an appropriate storage tier.
  • Treat bandwidth as a product feature. Size uplinks for concurrent node synchronization, backfills, replication, and API traffic.
  • Choose predictable, single‑tenant servers. Dedicated host resources make contention and capacity easier to manage.

Scale blockchain analytics with Melbicom

Deploy high‑core CPUs, NVMe storage, and networking up to 200 Gbps per server. Choose a single‑tenant configuration for your nodes, ETL, and OLAP workloads.

Explore plans

 

Back to the blog

Get expert support with your services

Phone, email, or Telegram: our engineers are available 24/7 to keep your workloads online.




    This site is protected by reCAPTCHA and the Google
    Privacy Policy and
    Terms of Service apply.