ARCHIVE/xrpl-dev-portal
1
0
Fork 0
mirror of https://github.com/XRPLF/xrpl-dev-portal.git synced 2025-11-21 04:05:49 +00:00
Code Issues Packages Projects Releases Wiki Activity
Files
f0945c3560af2034dd27ffb6d545c20ba7746912
xrpl-dev-portal/content/tutorials/manage-the-rippled-server/installation/system-requirements.md
mDuo13 f0945c3560 Capacity planning / system requirements updates 
- Move recommended specs first for people who skim
- Mention of automatic [node_size]
- No longer recommending RocksDB in any circumstance
- Reduced usage of the `rippled` name.
2021-11-24 14:41:12 -08:00

2.4 KiB
Raw Blame History

html, parent, blurb, labels
html parent blurb labels
system-requirements.html install-rippled.html Hardware and software requirements for running rippled.
Core Server

System Requirements

Recommended Specifications

For reliable performance in production environments, it is recommended to run an XRP Ledger (rippled) server on bare metal with the following characteristics:

  • Operating System: Ubuntu (LTS) or CentOS or RedHat Enterprise Linux (latest release)
  • CPU: Intel Xeon 3+ GHz processor with 8+ cores and hyperthreading enabled
  • Disk: SSD / NVMe (10,000 IOPS or better)
  • RAM: 64 GB
  • Network: Enterprise data center network with a gigabit network interface on the host

Minimum Specifications

For testing purposes or occasional use, you can run an XRP Ledger server should on commodity hardware. The following minimum requirements should work for most cases, but may not always stay synced with the network:

  • Operating System: Mac OS X, Windows (64-bit), or most Linux distributions (Red Hat, Ubuntu, and Debian supported)
  • CPU: 64-bit x86_64, 4+ cores
  • Disk: Minimum 50 GB for the database partition. SSD strongly recommended (minimum 1000 IOPS, more is better)
  • RAM: 16 GB+

Amazon EC2's m3.large VM size may be appropriate depending on your workload. A fast network connection is preferable. Any increase in a server's client-handling load increases resources needs.

System Time

A rippled server relies on maintaining accurate time. It is recommended that the system synchronize time using the Network Time Protocol (NTP) with daemons such as ntpd or chrony.

See Also

{% include '_snippets/rippled-api-links.md' %} {% include '_snippets/tx-type-links.md' %} {% include '_snippets/rippled_versions.md' %}