Capacity Planning

This section describes configuration, network, and hardware recommendations that you can use to tune and optimize the performance of your rippled server. Being aware of these considerations can help you ensure that your rippled server is ready to handle XRP Ledger network capacity today and in the near future.

Configuration Settings

Ripple recommends using these configuration guidelines to optimize resource utilization and performance of your rippled server.

You can set the following parameters in the rippled.cfg file used for your rippled server. You can access an example config file, rippled-example.cfg, in the cfg directory in the rippled GitHub repo.

Node Size

Set the node_size based on your server's expected load and the amount of memory you can make available to rippled.

Ripple recommends you always use the largest node size your available RAM can support. See the following table for recommended settings.


Each node_size has a corresponding requirement for available RAM. For example, if you set node_size to huge, you should have at least 32 GB of available RAM to help ensure that rippled can run smoothly.

To tune your server, it may be useful to start with tiny and increase the size to small, medium, and so on as you refine the requirements for your use case.

RAM available for rippled node_size value Notes
< 8 GB tiny Not recommended for testing or production servers. This is the default value if you don't specify a value in rippled.cfg.
8 GB small Recommended for test servers.
16 GB medium The rippled-example.cfg file uses this value.
64 GB huge Recommended for production servers.

Although large is also a legal value for [node_size], in practice it performs worse than huge in most circumstances. Ripple recommends always using huge instead of large. Always use huge if you want stability.

If you set the node_size parameter to an invalid value, the server fails to start.

Node DB Type

The type field in the [node_db] stanza of the rippled.cfg file sets the type of key-value store that rippled uses to hold the ledger store.

This setting does not directly configure RAM settings, but the choice of key-value store has important implications for RAM usage because of the different ways these technologies cache and index data for fast lookup.

You can set the value to either RocksDB or NuDB.

  • If your server is a validator, it only needs a small amount of history, so use RocksDB for best performance. Learn more

  • For most cases, use NuDB because its performance is constant even with large amounts of data on disk. A fast SSD is required. Learn more

  • If you are using rotational disks (not recommended) or an unusually slow SSD, use RocksDB. Learn more

The example rippled-example.cfg file has the type field in the [node_db] stanza set to RocksDB.

More About Using RocksDB

RocksDB is an persistent key-value store built into rippled.

RocksDB works well on solid-state disks. RocksDB performs better than NuDB when used with rotational disks, but you may still encounter performance problems unless you use solid-state disks.

RocksDB requires approximately one-third less disk storage than NuDB and provides better I/O latency. However, the better I/O latency comes as result of the large amount of RAM RocksDB requires to store data indexes.

Validators should be configured to use RocksDB and to store no more than about 300,000 ledgers (approximately two weeks' worth of historical data) in the ledger store.

RocksDB has performance-related configuration options that you can set in rippled.cfg to achieve maximum transaction processing throughput. Here is the recommended configuration for a rippled server using RocksDB:


(Adjust the path to the directory where you want to keep the ledger store on disk. Adjust the online_delete and advisory_delete settings as desired for your configuration.)

More About Using NuDb

NuDB is an append-only key-value store that is optimized for SSD drives.

NuDB has nearly constant performance and memory footprints regardless of the amount of data being stored. NuDB requires a solid-state drive, but uses much less RAM than RocksDB to access a large database.

Non-validator production servers should be configured to use NuDB and to store the amount of historical data required for the use case.

NuDB does not have performance-related configuration options available in rippled.cfg. Here is the recommended configuration for a rippled server using NuDB:


(Adjust the path to the directory where you want to keep the ledger store on disk. Adjust the online_delete and advisory_delete settings as desired for your configuration.)

Log Level

The example rippled-example.cfg file sets the logging verbosity to warning in the [rpc_startup] stanza. This setting greatly reduces disk space and I/O requirements over more verbose logging. However, more verbose logging provides increased visibility for troubleshooting.

Caution: If you omit the log_level command from the [rpc_startup] stanza, rippled writes logs to disk at the debug level and outputs warning level logs to the console. debug level logging requires several more GB of disk space per day than warning level, depending on transaction volumes and client activity.

Network and Hardware

Each rippled server in the XRP Ledger network performs all of the transaction processing work of the network. Therefore, the baseline hardware for production rippled servers should be similar to that used in Ripple's performance testing .

Ensuring that your rippled server meets these network and hardware requirements helps achieve consistent, good performance across the XRP Ledger network.


For best performance in enterprise production environments, Ripple recommends running rippled on bare metal with the following characteristics:

  • Operating System: Ubuntu 16.04+
  • CPU: Intel Xeon 3+ GHz processor with 4 cores and hyperthreading enabled
  • Disk speed: SSD (10,000 IOPS)
  • Disk space: Varies. At least 50 GB recommended.
  • RAM: 64 GB
  • Network: Enterprise data center network with a gigabit network interface on the host

CPU Utilization and Virtualization

You'll get the best performance on bare metal, but virtual machines can perform nearly as well as long as the host hardware has high enough specs.

Disk Speed

Ripple strongly recommends using a high-grade solid state disk drive (SSD) with low-latency random reads and high throughput. Ripple engineers have observed the following maximum reads and writes per second:

  • Over 10,000 reads per second (in heavily-used public server clusters)
  • Over 7,000 writes per second (in dedicated performance testing)

Disk Space

The amount of disk space rippled requires depend on how much ledger history you plan to keep available locally. A rippled server does not need to store more than the most recent 256 ledger versions to follow the consensus process and report the complete state of the ledger, but you can only query your server for transactions that executed in ledger versions it has stored locally.

You can control how much data you keep with online deletion; the default config file has the server keep the latest 2000 ledger versions. Without online deletion, the server's disk requirements grow without bounds.

The following table approximates the requirements for different amounts of history, at the time of writing (2018-12-13):

Real Time Amount Number of Ledger Versions Disk Space Required (RocksDB) Disk Space Required (NuDB)
2 hours 2,000 250 MB 450 MB
1 day 25,000 8 GB 12 GB
14 days 350,000 112 GB 168 GB
30 days 750,000 240 GB 360 GB
90 days 2,250,000 720 GB 1 TB
1 year 10,000,000 3 TB 4.5 TB
2 years 20,000,000 6 TB 9 TB
Full history (as of 2020-11-10) 59,000,000+ (Not recommended) ~14 TB

These numbers are estimates. They depend on several factors, most importantly the volume of transactions in the network. As transaction volume increases, each ledger version stores more unique data. You should provision extra storage capacity to prepare for future growth.

The online_delete setting tells the server how many ledger versions to keep after deleting old history. You should plan for enough disk space to store twice that many ledger versions at maximum (right before online deletion runs).

For instructions on how to change the amount of history you keep, see Configure Online Deletion.

If you want to contribute to storing ledger history but you do not have enough disk space to store full history, you can use the History Sharding feature to store a randomized range of ledgers in a separate shard store. History sharding is configured in the [shard_db] stanza, and it can use a different type of key-value store than the one you defined for the ledger store using the [node_db] stanza.

Amazon Web Services

Amazon Web Services (AWS) is a popular virtualized hosting environment. You can run rippled in AWS, but if using Elastic Block Storage (EBS), only use either the io1 or io2 types, and configure them for at least 10,000 IOPS. Alternately, AWS instance stores (ephemeral storage) also has suitable performance. However, that is not durable, so data loss is to be expected under some circumstances. The database_path and node_db path should each reside on either EBS io1 or io2, or on instance storage.

Caution: AWS instance storage is not guaranteed to provide durability in the event of hard drive failure. You also lose data when you stop/start or reboot the instance. The latter type of data loss can be acceptable for a rippled server because an individual server can usually re-acquire the lost data from its peer servers.


Memory requirements are mainly a function of the node_size configuration setting and the amount of client traffic retrieving historical data. For more information about memory requirements, see Node Size.


Any enterprise or carrier-class data center should have substantial network bandwidth to support running rippled servers. The actual bandwidth necessary varies significantly based on the current transaction volume in the network. Server behavior (such as backfilling ledger history) also affects network use.

During exceptionally high periods of transaction volume, some operators have reported that their rippled servers have completely saturated a 100 megabit/s network link. Therefore, a gigabit network interface is required for reliable performance.

Here are examples of observed uncompressed network bandwidth use for common rippled tasks:

Task Transmit/Receive
Process average transaction volumes 2 Mbps transmit, 2 Mbps receive
Process peak transaction volumes >100 Mbps transmit
Serve historical ledger and transaction reports 100 Mbps transmit
Start up rippled 20 Mbps receive

You can save bandwidth by enabling compression on peer-to-peer communications, at a cost of higher CPU. Many hardware configurations have spare CPU capacity during normal use, so this can be an economical option if your network bandwidth is limited.

See Also