From 892689444988997ae7488afc10064c28a90b8432 Mon Sep 17 00:00:00 2001 From: amarantha-k Date: Thu, 27 Jul 2023 18:08:48 +0000 Subject: [PATCH] deploy: 02ba7250829b88255b3f396c24e49468df7d4c9e --- .../build-a-desktop-wallet-in-python.html | 5 +- pr-preview/fixTypos/capacity-planning.html | 43 ++++-- .../fixTypos/configure-full-history.html | 3 +- .../img/ecosystem-apps-and-services.svg | 140 +++++++++--------- .../img/ecosystem-client-libraries.svg | 41 +++++ .../fixTypos/img/ecosystem-middleware.svg | 121 +++++++-------- .../fixTypos/img/ecosystem-peer-to-peer.svg | 65 ++++---- .../img/ecosystem-programming-libraries.svg | 43 ------ .../ja/build-a-desktop-wallet-in-python.html | 5 +- .../ja/img/ecosystem-apps-and-services.svg | 140 +++++++++--------- .../ja/img/ecosystem-client-libraries.svg | 41 +++++ .../fixTypos/ja/img/ecosystem-middleware.svg | 121 +++++++-------- .../ja/img/ecosystem-peer-to-peer.svg | 65 ++++---- .../img/ecosystem-programming-libraries.svg | 43 ------ pr-preview/fixTypos/software-ecosystem.html | 2 +- pr-preview/fixTypos/style_report.txt | 107 ++++++------- pr-preview/fixTypos/system-requirements.html | 2 +- 17 files changed, 496 insertions(+), 491 deletions(-) create mode 100644 pr-preview/fixTypos/img/ecosystem-client-libraries.svg delete mode 100644 pr-preview/fixTypos/img/ecosystem-programming-libraries.svg create mode 100644 pr-preview/fixTypos/ja/img/ecosystem-client-libraries.svg delete mode 100644 pr-preview/fixTypos/ja/img/ecosystem-programming-libraries.svg diff --git a/pr-preview/fixTypos/build-a-desktop-wallet-in-python.html b/pr-preview/fixTypos/build-a-desktop-wallet-in-python.html index 41fd5c759a8..9d719d8bbc2 100644 --- a/pr-preview/fixTypos/build-a-desktop-wallet-in-python.html +++ b/pr-preview/fixTypos/build-a-desktop-wallet-in-python.html @@ -321,7 +321,7 @@

Goals

tokens or use other payment types like Escrow or Payment Channels. However, it provides a foundation that you can implement those and other features on top of.

-

Other topics mentioned in this tutorial include graphical user interface (GUI) programming, threading, and asynchronous (async) code in Python.

+

In addition to the above features, you'll also learn a little bit about graphical user interface (GUI) programming, threading, and asynchronous (async) code in Python.

Steps

Install Dependencies

This tutorial depends on various programming libraries. Before you get started coding, you should install all of them as follows:

@@ -339,6 +339,7 @@

Install Dependencies

On Windows, you can build apps using either Windows natively or by using the Windows Subsystem for Linux (WSL).

On native Windows, the GUI uses native Windows controls and should run without any dependencies beyond those mentioned above.

+

Caution: As of 2022-02-01, the latest wxPython is not compatible with Python 3.10 on Windows. You should be able to follow this tutorial if you downgrade to the latest release of Python 3.9.

On WSL, you may need to install libnotify-dev as follows:

apt-get install libnotify-dev
@@ -523,7 +524,7 @@

2. Show Ledger Updates

run your own rippled server you can connect to it using ws://localhost:6006 as the URL. You can also use the WebSocket URLs of public servers to connect to the Mainnet or other test networks.

Troubleshooting SSL Certificate Errors

If you get an error like this, you may need to make sure your operating system's certificate authority store is updated:

diff --git a/pr-preview/fixTypos/capacity-planning.html b/pr-preview/fixTypos/capacity-planning.html index aee8aa18c80..cc13c293de6 100644 --- a/pr-preview/fixTypos/capacity-planning.html +++ b/pr-preview/fixTypos/capacity-planning.html @@ -352,13 +352,21 @@

Recommendationserver 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.

-

For almost all purposes, use NuDB. A fast SSD is required. Learn more

-

The RocksDB setting is available for legacy purposes, but is generally not recommended. Learn more

+

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.

+
    +
  • +

    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. You should avoid this setting for production servers. Learn more

    +
    • +

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

More About Using RocksDB

-

RocksDB is a persistent key-value store built into rippled. Support for RocksDB is considered legacy. Servers using RocksDB usually struggle to maintain sync with the Mainnet due to the memory requirements of maintaining a large database. Generally, you should use NuDB instead.

-

Cases where you might use RocksDB include if you need to load historical data saved in RocksDB format, or if you are storing data on slow SSDs or rotational disks. While rotational disks won't be able to keep up with Mainnet, you can probably run offline tests or small private networks on them.

-

RocksDB has performance-related configuration options that you can tweak for more transaction processing throughput. Here is an example [node_db] configuration for RocksDB:

+

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

+

Caution: As of late 2021, the total size of the ledger has grown large enough that servers using RocksDB often struggle to maintain sync with the Mainnet. Large amounts of RAM can help, but you should generally use NuDB instead.

+

RocksDB is intended to work on either solid-state disks or rotational disks. It 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.

+

RocksDB has performance-related configuration options that you can tweak for more transaction processing throughput. Here is a recommended [node_db] configuration for RocksDB:

[node_db]
 type=RocksDB
 path=/var/lib/rippled/db/rocksdb
@@ -371,10 +379,10 @@ 
More About Using RocksDB

+

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. Scalability testing has shown that NuDB has equivalent or better performance than RocksDB in production and comparable configurations.

-

Production servers should be configured to use NuDB and to store the amount of historical data required for your use case.

+

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.

+

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 [node_db] configuration for a rippled server using NuDB:

[node_db]
 type=NuDB
@@ -382,7 +390,7 @@ 
More About Using NuDB

Configure Online Deletion and Configure Advisory Deletion.

+

(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, the server writes logs to disk at the debug level and outputs warning level logs to the console. Logging at the debug level requires several more GB of disk space per day than warning level, depending on transaction volumes and client activity.

@@ -403,12 +411,13 @@

Disk Speed

The [node_db] stanza controls the server's ledger store, which holds ledger history. The amount of disk space you need depends on how much history you plan to keep available locally. An XRP Ledger 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. Configure the path of the [node_db] to point to your chosen storage location for the ledger store.

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 (2023-07-19):

+

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

+ @@ -416,42 +425,50 @@

Disk Space

Real Time Amount Number of Ledger VersionsDisk Space Required (RocksDB) Disk Space Required (NuDB)
2,000250 MB 450 MB
1 day 25,0008 GB 12 GB
14 days 350,000112 GB 168 GB
30 days 750,000240 GB 360 GB
90 days 2,250,000720 GB 1 TB
1 year 10,000,0003 TB 4.5 TB
2 years 20,000,0006 TB 9 TB
Full history81,000,000+~26 TBFull history (as of 2022-12-18)76,500,000+(Not recommended)~22.3 TB

In its default configuration, the rippled server automatically deletes outdated history of XRP Ledger state and transactions as new ledger versions become available. This is enough for most servers, which do not need older history to know the current state and process transactions. However, it can be useful for the network if some servers provide as much history of the XRP Ledger as possible.

Warnings

-

Storing full history is expensive. As of 2023-07-19, the full history of the XRP Ledger occupies approximately 26 terabytes of disk space, which must be entirely stored on fast solid state disk drives for proper server performance. Such a large amount of solid state storage is not cheap, and the total amount of history you must store increases by approximately 12 GB per day.

-

Additionally, storing full history in NuDB requires single files that are larger than the 16 TB limit of ext4 filesystems, which is the default on many Linux distributions. You must use a filesystem with a larger single-file limit, such as XFS (recommended) or ZFS.

+

Storing full history is expensive. As of 2020-11-10, the full history of the XRP Ledger occupies approximately 14 terabytes of disk space, which must be entirely stored on fast solid state disk drives for proper server performance. Such a large amount of solid state storage is not cheap, and the total amount of history you must store increases by approximately 12 GB per day.

Acquiring full history from the peer-to-peer network takes a long time (several months) and requires that your server has enough system and network resources to acquire older history while keeping up with new ledger progress. To get a faster start on acquiring ledger history, you may want to find another server operator who has a large amount of history already downloaded, who can give you a database dump or at least allow your server to explicitly peer with theirs for a long time to acquire history. The server can load ledger history from a file and verify the integrity of the historical ledgers it imports.

You do not need a full history server to participate in the network, validate transactions, or know the current state of the network. Full history is only useful for knowing the outcome of transactions that occurred in the past, or the state of the ledger at a given time in the past. To get such information, you must rely on other servers having the history you need.

If you want to contribute to storing the history of the XRP Ledger network without storing the full history, you can configure history sharding to store randomly-selected chunks of ledger history instead.

diff --git a/pr-preview/fixTypos/img/ecosystem-apps-and-services.svg b/pr-preview/fixTypos/img/ecosystem-apps-and-services.svg index 3e69a0b8200..11f97decdcd 100644 --- a/pr-preview/fixTypos/img/ecosystem-apps-and-services.svg +++ b/pr-preview/fixTypos/img/ecosystem-apps-and-services.svg @@ -1,72 +1,74 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + - - - - - - + + + + + + + - - - - - - - - - - - - - - - - - - - - - - - - - + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/pr-preview/fixTypos/img/ecosystem-client-libraries.svg b/pr-preview/fixTypos/img/ecosystem-client-libraries.svg new file mode 100644 index 00000000000..126bcc1adfc --- /dev/null +++ b/pr-preview/fixTypos/img/ecosystem-client-libraries.svg @@ -0,0 +1,41 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/pr-preview/fixTypos/img/ecosystem-middleware.svg b/pr-preview/fixTypos/img/ecosystem-middleware.svg index db235838e3f..31a3a07f888 100644 --- a/pr-preview/fixTypos/img/ecosystem-middleware.svg +++ b/pr-preview/fixTypos/img/ecosystem-middleware.svg @@ -1,63 +1,64 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - + + + + + + + + + + + + + + + + + + + + + + + + + + + - - - - - - - - - - - + + + + + + + - - - - - - - - - - - - + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/pr-preview/fixTypos/img/ecosystem-peer-to-peer.svg b/pr-preview/fixTypos/img/ecosystem-peer-to-peer.svg index 8f04430876e..316daf7209a 100644 --- a/pr-preview/fixTypos/img/ecosystem-peer-to-peer.svg +++ b/pr-preview/fixTypos/img/ecosystem-peer-to-peer.svg @@ -1,36 +1,33 @@ - - - - - - - - - - - - - - + + + + + + + + + + + + - - - - - - - - - - - - - - - - - - - - + + + + + + + + + + + + + + + + + + + diff --git a/pr-preview/fixTypos/img/ecosystem-programming-libraries.svg b/pr-preview/fixTypos/img/ecosystem-programming-libraries.svg deleted file mode 100644 index f00242c4711..00000000000 --- a/pr-preview/fixTypos/img/ecosystem-programming-libraries.svg +++ /dev/null @@ -1,43 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - diff --git a/pr-preview/fixTypos/ja/build-a-desktop-wallet-in-python.html b/pr-preview/fixTypos/ja/build-a-desktop-wallet-in-python.html index b077804d023..0a6ab2a033d 100644 --- a/pr-preview/fixTypos/ja/build-a-desktop-wallet-in-python.html +++ b/pr-preview/fixTypos/ja/build-a-desktop-wallet-in-python.html @@ -328,7 +328,7 @@

Goals

tokens or use other payment types like Escrow or Payment Channels. However, it provides a foundation that you can implement those and other features on top of.

-

Other topics mentioned in this tutorial include graphical user interface (GUI) programming, threading, and asynchronous (async) code in Python.

+

In addition to the above features, you'll also learn a little bit about graphical user interface (GUI) programming, threading, and asynchronous (async) code in Python.

Steps

Install Dependencies

This tutorial depends on various programming libraries. Before you get started coding, you should install all of them as follows:

@@ -346,6 +346,7 @@

Install Dependencies

On Windows, you can build apps using either Windows natively or by using the Windows Subsystem for Linux (WSL).

On native Windows, the GUI uses native Windows controls and should run without any dependencies beyond those mentioned above.

+

Caution: As of 2022-02-01, the latest wxPython is not compatible with Python 3.10 on Windows. You should be able to follow this tutorial if you downgrade to the latest release of Python 3.9.

On WSL, you may need to install libnotify-dev as follows:

apt-get install libnotify-dev
@@ -530,7 +531,7 @@

2. Show Ledger Updates

run your own rippled server you can connect to it using ws://localhost:6006 as the URL. You can also use the WebSocket URLs of public servers to connect to the Mainnet or other test networks.

Troubleshooting SSL Certificate Errors

If you get an error like this, you may need to make sure your operating system's certificate authority store is updated:

diff --git a/pr-preview/fixTypos/ja/img/ecosystem-apps-and-services.svg b/pr-preview/fixTypos/ja/img/ecosystem-apps-and-services.svg index 3e69a0b8200..11f97decdcd 100644 --- a/pr-preview/fixTypos/ja/img/ecosystem-apps-and-services.svg +++ b/pr-preview/fixTypos/ja/img/ecosystem-apps-and-services.svg @@ -1,72 +1,74 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + - - - - - - + + + + + + + - - - - - - - - - - - - - - - - - - - - - - - - - + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/pr-preview/fixTypos/ja/img/ecosystem-client-libraries.svg b/pr-preview/fixTypos/ja/img/ecosystem-client-libraries.svg new file mode 100644 index 00000000000..126bcc1adfc --- /dev/null +++ b/pr-preview/fixTypos/ja/img/ecosystem-client-libraries.svg @@ -0,0 +1,41 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/pr-preview/fixTypos/ja/img/ecosystem-middleware.svg b/pr-preview/fixTypos/ja/img/ecosystem-middleware.svg index db235838e3f..31a3a07f888 100644 --- a/pr-preview/fixTypos/ja/img/ecosystem-middleware.svg +++ b/pr-preview/fixTypos/ja/img/ecosystem-middleware.svg @@ -1,63 +1,64 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - + + + + + + + + + + + + + + + + + + + + + + + + + + + - - - - - - - - - - - + + + + + + + - - - - - - - - - - - - + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/pr-preview/fixTypos/ja/img/ecosystem-peer-to-peer.svg b/pr-preview/fixTypos/ja/img/ecosystem-peer-to-peer.svg index 8f04430876e..316daf7209a 100644 --- a/pr-preview/fixTypos/ja/img/ecosystem-peer-to-peer.svg +++ b/pr-preview/fixTypos/ja/img/ecosystem-peer-to-peer.svg @@ -1,36 +1,33 @@ - - - - - - - - - - - - - - + + + + + + + + + + + + - - - - - - - - - - - - - - - - - - - - + + + + + + + + + + + + + + + + + + + diff --git a/pr-preview/fixTypos/ja/img/ecosystem-programming-libraries.svg b/pr-preview/fixTypos/ja/img/ecosystem-programming-libraries.svg deleted file mode 100644 index f00242c4711..00000000000 --- a/pr-preview/fixTypos/ja/img/ecosystem-programming-libraries.svg +++ /dev/null @@ -1,43 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - diff --git a/pr-preview/fixTypos/software-ecosystem.html b/pr-preview/fixTypos/software-ecosystem.html index fbe5c03874e..d884a86f94b 100644 --- a/pr-preview/fixTypos/software-ecosystem.html +++ b/pr-preview/fixTypos/software-ecosystem.html @@ -318,7 +318,7 @@

Core ServersHTTP / WebSocket APIs for users to look up data, administer the server, and submit transactions. Some servers also serve HTTP / WebSocket APIs but don't connect directly to the peer-to-peer network and don't process transactions or participate in consensus. These servers, such as rippled servers running in Reporting Mode and Clio servers, rely on a core server in P2P mode to process transactions.

Client Libraries

Libraries simplify some of the common work of accessing the XRP Ledger, usually through the HTTP / WebSocket APIs. They convert the data into forms that are more familiar and convenient for various programming languages, and include implementations of common operations. Some client libraries are officially maintained by the XRP Ledger Foundation and some are maintained by other entities in the community.

-

Client Libraries

+

Client Libraries

One core feature of most client libraries is signing transactions locally, so users never have to send their private key across any network.

Many middleware services use client libraries internally.

See Client Libraries for some information about currently available client libraries.

diff --git a/pr-preview/fixTypos/style_report.txt b/pr-preview/fixTypos/style_report.txt index d735886a3dd..41d0e8f1684 100644 --- a/pr-preview/fixTypos/style_report.txt +++ b/pr-preview/fixTypos/style_report.txt @@ -1,15 +1,15 @@ ------------- Spell Checker ------------- -Found 136 possible spelling errors: +Found 131 possible spelling errors: Unknown Words: - gifs: gips, giff, gifu + gifs: gibs, gins, gifu ringtee: kuressaare: lõõtsa: Unknown Words: - livenet: livened, livener + livenet: livener, livened Unknown Words: opencoin: @@ -20,14 +20,14 @@ Found 136 possible spelling errors: Unknown Words: transactiontype: - rf1bigexwwqoi8z2uefytexswujyfv2jpn: ra5nk24kxen9ahvsdftkhsaninzsewnpcx: + rf1bigexwwqoi8z2uefytexswujyfv2jpn: Unknown Words: requiremen: requirement Unknown Words: - xapps: lapps, capps, apps + xapps: apps, capps, lapps Unknown Words: arweave: @@ -37,15 +37,15 @@ Found 136 possible spelling errors: tokentaxon: Unknown Words: - investopedia: arbitraging: arbitrating + investopedia: unprecented: unprevented, unpresented - clob: clomb, cloy, lob - 30d: 3d, 3-d, 3rd + clob: colb, club, slob + 30d: 3d, 3rd, 3-d frontrunning: Unknown Words: - v3: v1, vo, vj + v3: v8, vp, vg 0b0: Unknown Words: @@ -53,18 +53,18 @@ Found 136 possible spelling errors: Unknown Words: xrpfees: - fixnftokenremint: - fixuniversalnumber: - fixnonfungibletokensv1_2: - depositpreauthamendment: disallowincoming: + fixnonfungibletokensv1_2: + fixuniversalnumber: immediateofferkilled: + fixnftokenremint: + depositpreauthamendment: nftokenoffers: nftokenoffer - asfdisallowincomingcheck: asfdisallowincomingnftoffer: asfdisallowincomingpaychan: asfdisallowincomingtrustline: - 30d: 3d, 3-d, 3rd + asfdisallowincomingcheck: + 30d: 3d, 3rd, 3-d Unknown Words: xlsd: lsd, xls @@ -74,7 +74,7 @@ Found 136 possible spelling errors: nftokencounttracking: Unknown Words: - ooffers: doffers, goffers, coffers + ooffers: offers, goffers, coffers Unknown Words: 24n: @@ -95,53 +95,53 @@ Found 136 possible spelling errors: Unknown Words: nft_history: - slas: sas, slap, elas + slas: stas, slay, blas Unknown Words: - 30d: 3d, 3-d, 3rd + 30d: 3d, 3rd, 3-d Unknown Words: - mod1: mode, modi, mod + mod1: mod, mody, modo get_account: get_account_info: send_xrp: - lesson1: lesson, lessons + lesson1: lessons, lesson tkinter: tinter, twinter getstandbyaccount: get_standby_account_info: standby_send_xrp: Unknown Words: - mod2: mode, modi, mod + mod2: mod, mody, modo send_currency: get_balance: configure_account: - lesson2: lesson, lessons + lesson2: lessons, lesson Unknown Words: - mod3: mode, modi, mod + mod3: mod, mody, modo minttoken: gettokens: burn_token: Unknown Words: - mod4: mode, modi, mod + mod4: mod, mody, modo offer___index: alloffers: - lesson4: lesson, lessons + lesson4: lessons, lesson Unknown Words: - sell___offer___index: - broker___fee: buy___offer___index: - lesson5: lesson, lessons + broker___fee: + sell___offer___index: + lesson5: lessons, lesson Unknown Words: - mod6: mode, modi, mod + mod6: mod, mody, modo mint_other: Unknown Words: - ripple8: rippled, ripple, rippler + ripple8: ripples, ripplet, rippled numofseconds: offersequence: @@ -159,7 +159,7 @@ Found 136 possible spelling errors: Unknown Words: networkid: networked - v3: v1, vo, vj + v3: v8, vp, vg Unknown Words: disallowincoming: @@ -170,8 +170,8 @@ Found 136 possible spelling errors: disallowincoming: Unknown Words: - nftokenoffers: nftokenoffer disallowincoming: + nftokenoffers: nftokenoffer Unknown Words: immediateofferkilled: @@ -194,46 +194,37 @@ Found 136 possible spelling errors: Unknown Words: nft_history: - Unknown Words: - scalability: salability - - Unknown Words: - filesystems: filesystem - zfs: rfs, zgs, lfs - ext4: ext., ext, exta - xfs: rfs, xs, lfs - Unknown Words: - img: imt, bmg, im + scss: scsa, sss, sccs _snippets: snippets - scss: sass, scts, sss + umlet: mulet, unlet, umset + img: qmg, ig, imm _img: - umlet: umset, mulet, unlet _code: code frontmatter: dropdown: dropdowns: santilli: - h1: v1, hw, l1 - postgres: postures + h1: hy, hb, hq + websockets: websocket + nif: rif, naif, nix camelcase: + postgres: postures + xrps: xrp, xrpl, rps orderbook: order-book - websockets: websocket trustline: - nif: nit, nsf, nib - xrps: xrpl, xrp, rps Unknown Words: hyperlinks: bcp47: - zh: zi, ah, zr - utf: dtf, ntf, atf + zh: dh, zd, zo + utf: uhf, utr, wtf Unknown Words: subfolder: subfolders - inlined: inline, unlined, inclined - umlet: umset, mulet, unlet - scss: sass, scts, sss + inlined: unlined, inline, inclined + umlet: mulet, unlet, umset + scss: scsa, sss, sccs Unknown Words: screenshots: screenshot @@ -431,7 +422,7 @@ Page Length Metrics Average Page Length Metrics: Sentences: 55 Words: 726 - Characters: 4,508 + Characters: 4,509 Longest pages by character count: Length Metrics: @@ -445,9 +436,9 @@ Longest pages by character count: Characters: 40,005 Length Metrics: - Sentences: 297 - Words: 5,143 - Characters: 29,332 + Sentences: 299 + Words: 5,187 + Characters: 29,549 Shortest pages by character count: Length Metrics: diff --git a/pr-preview/fixTypos/system-requirements.html b/pr-preview/fixTypos/system-requirements.html index c33c9548632..8b46361053c 100644 --- a/pr-preview/fixTypos/system-requirements.html +++ b/pr-preview/fixTypos/system-requirements.html @@ -297,7 +297,7 @@

System Requirements

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

    -
  • Operating System: Ubuntu (LTS), Red Hat Enterprise Linux (latest release), or a compatible Linux distribution.
    • +
  • Operating System: Ubuntu (LTS) or CentOS or Red Hat Enterprise Linux (latest release).
  • CPU: Intel Xeon 3+ GHz processor with 8+ cores and hyperthreading enabled.
  • Disk: SSD / NVMe (10,000 IOPS sustained - not burst or peak - or better). Minimum 50 GB for the database partition. Do not use Amazon Elastic Block Store (AWS EBS) because its latency is too high to sync reliably.
  • RAM: 64 GB.