ARCHIVE/xrpl-dev-portal
1
0
Fork 0
mirror of https://github.com/XRPLF/xrpl-dev-portal.git synced 2025-11-25 14:15:50 +00:00
Code Issues Packages Projects Releases Wiki Activity

fixed col headers

Browse Source
This commit is contained in:
Jennifer Hasegawa
2018-12-10 18:04:26 -08:00
parent 17a0f846d9
commit c9c5fbfdf1
1 changed files with 6 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files

12
content/tutorials/manage-the-rippled-server/installation/capacity-planning.md
View File

@@ -23,12 +23,12 @@ Each `node_size` has a corresponding requirement for available RAM. For example,
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.
| `node_size` value | RAM available for `rippled` | Notes |
|:------------------|:----------------------------|:---------------------------|
| < 8GB | `tiny` | Not recommended for testing or production servers. If not specified in `rippled.cfg`, `tiny` is the default value. |
| 8GB | `small` | Recommended for test servers. |
| 16GB | `medium` | Note that the `rippled-example.cfg` has its `node_size` value set to `medium`. |
| 32GB | `huge` | Recommended for production servers. |
| RAM available for `rippled` | `node_size` value | Notes |
|:----------------------------|:------------------|:---------------------------|
| < 8GB | `tiny` | Not recommended for testing or production servers. This is the default value if you don't specify a value in `rippled.cfg`. |
| 8GB | `small` | Recommended for test servers. |
| 16GB | `medium` | The `rippled-example.cfg` file uses this value. |
| 32GB | `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`.