mirror of
https://github.com/XRPLF/xrpl-dev-portal.git
synced 2025-11-21 12:15:50 +00:00
@@ -13,6 +13,7 @@ A `rippled` server should run comfortably on commodity hardware, to make it inex
|
|||||||
|
|
||||||
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.
|
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.
|
||||||
|
|
||||||
|
|
||||||
## Recommended Specifications
|
## Recommended Specifications
|
||||||
|
|
||||||
For best performance in enterprise production environments, Ripple recommends running `rippled` on bare metal with the following characteristics:
|
For best performance in enterprise production environments, Ripple recommends running `rippled` on bare metal with the following characteristics:
|
||||||
@@ -25,6 +26,10 @@ For best performance in enterprise production environments, Ripple recommends ru
|
|||||||
- For production: 32GB
|
- For production: 32GB
|
||||||
- Network: Enterprise data center network with a gigabit network interface on the host
|
- Network: Enterprise data center network with a gigabit network interface on the host
|
||||||
|
|
||||||
|
## 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
|
## See Also
|
||||||
|
|
||||||
For more information on the recommended specifications and planning for production needs, see [Capacity Planning](capacity-planning.html).
|
For more information on the recommended specifications and planning for production needs, see [Capacity Planning](capacity-planning.html).
|
||||||
|
|||||||
Reference in New Issue
Block a user