From 76925b6c4f686e05ec2259c2d04900ee770cbaf8 Mon Sep 17 00:00:00 2001 From: Jennifer Hasegawa Date: Mon, 29 Oct 2018 11:25:52 -0700 Subject: [PATCH 1/3] updated full history TB --- .../tutorials/manage-the-rippled-server/capacity-planning.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/content/tutorials/manage-the-rippled-server/capacity-planning.md b/content/tutorials/manage-the-rippled-server/capacity-planning.md index 23842c6e40..1a593bc607 100644 --- a/content/tutorials/manage-the-rippled-server/capacity-planning.md +++ b/content/tutorials/manage-the-rippled-server/capacity-planning.md @@ -57,7 +57,7 @@ path={path_to_ledger_store} ### Historical Data -The amount of historical data that a `rippled` server keeps online is a major contributor to required storage space. At the time of writing (2018-03-01), a `rippled` server stores about 12GB of data per day. You can expect this amount to grow as transaction volume increases across the XRP Ledger network. You can control how much data you keep with the `online_delete` and `advisory_delete` fields. +The amount of historical data that a `rippled` server keeps online is a major contributor to required storage space. At the time of writing (2018-05-30), a `rippled` server stores about 12GB of data per day and requires 7.9TB to store the full history of the XRP Ledger. You can expect this amount to grow as transaction volume increases across the XRP Ledger network. You can control how much data you keep with the `online_delete` and `advisory_delete` fields. Online deletion enables pruning of `rippled` ledgers from databases without any disruption of service. It only removes records that are not part of the current ledgers. Without online deletion, those databases grow without bounds. Freeing disk space requires stopping the process and manually removing database files. @@ -98,7 +98,7 @@ Any enterprise or carrier-class data center should have substantial network band #### Storage -Ripple recommends estimating storage sizing at roughly 12GB per day of data kept online with NuDB. RocksDB requires around 8GB per day. However, the data per day changes with activity in the network. You should provision extra capacity to prepare for future growth. At the time of writing (2018-03-01), a server with all XRP Ledger history requires 6.8TB. +Ripple recommends estimating storage sizing at roughly 12GB per day of data kept online with NuDB. RocksDB requires around 8GB per day. However, the data per day changes with activity in the network. You should provision extra capacity to prepare for future growth. At the time of writing (2018-05-30), a server with all XRP Ledger history requires 7.9TB. From ce84d58a8492d178c89c18ecb06605e1aceac04f Mon Sep 17 00:00:00 2001 From: Jennifer Hasegawa Date: Tue, 30 Oct 2018 09:59:04 -0700 Subject: [PATCH 2/3] update tb --- .../tutorials/manage-the-rippled-server/capacity-planning.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/content/tutorials/manage-the-rippled-server/capacity-planning.md b/content/tutorials/manage-the-rippled-server/capacity-planning.md index 1a593bc607..c950a6955b 100644 --- a/content/tutorials/manage-the-rippled-server/capacity-planning.md +++ b/content/tutorials/manage-the-rippled-server/capacity-planning.md @@ -57,7 +57,7 @@ path={path_to_ledger_store} ### Historical Data -The amount of historical data that a `rippled` server keeps online is a major contributor to required storage space. At the time of writing (2018-05-30), a `rippled` server stores about 12GB of data per day and requires 7.9TB to store the full history of the XRP Ledger. You can expect this amount to grow as transaction volume increases across the XRP Ledger network. You can control how much data you keep with the `online_delete` and `advisory_delete` fields. +The amount of historical data that a `rippled` server keeps online is a major contributor to required storage space. At the time of writing (2018-10-30), a `rippled` server stores about 12GB of data per day and requires 8.4TB to store the full history of the XRP Ledger. You can expect this amount to grow as transaction volume increases across the XRP Ledger network. You can control how much data you keep with the `online_delete` and `advisory_delete` fields. Online deletion enables pruning of `rippled` ledgers from databases without any disruption of service. It only removes records that are not part of the current ledgers. Without online deletion, those databases grow without bounds. Freeing disk space requires stopping the process and manually removing database files. @@ -98,7 +98,7 @@ Any enterprise or carrier-class data center should have substantial network band #### Storage -Ripple recommends estimating storage sizing at roughly 12GB per day of data kept online with NuDB. RocksDB requires around 8GB per day. However, the data per day changes with activity in the network. You should provision extra capacity to prepare for future growth. At the time of writing (2018-05-30), a server with all XRP Ledger history requires 7.9TB. +Ripple recommends estimating storage sizing at roughly 12GB per day of data kept online with NuDB. RocksDB requires around 8GB per day. However, the data per day changes with activity in the network. You should provision extra capacity to prepare for future growth. At the time of writing (2018-10-30), a server with all XRP Ledger history requires 8.4TB. From e0da4dac4e410145251630ad399c9d53b98e63a1 Mon Sep 17 00:00:00 2001 From: Jennifer Hasegawa Date: Tue, 30 Oct 2018 10:03:02 -0700 Subject: [PATCH 3/3] update tb date --- .../tutorials/manage-the-rippled-server/capacity-planning.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/content/tutorials/manage-the-rippled-server/capacity-planning.md b/content/tutorials/manage-the-rippled-server/capacity-planning.md index c950a6955b..3364ad6d73 100644 --- a/content/tutorials/manage-the-rippled-server/capacity-planning.md +++ b/content/tutorials/manage-the-rippled-server/capacity-planning.md @@ -57,7 +57,7 @@ path={path_to_ledger_store} ### Historical Data -The amount of historical data that a `rippled` server keeps online is a major contributor to required storage space. At the time of writing (2018-10-30), a `rippled` server stores about 12GB of data per day and requires 8.4TB to store the full history of the XRP Ledger. You can expect this amount to grow as transaction volume increases across the XRP Ledger network. You can control how much data you keep with the `online_delete` and `advisory_delete` fields. +The amount of historical data that a `rippled` server keeps online is a major contributor to required storage space. At the time of writing (2018-10-29), a `rippled` server stores about 12GB of data per day and requires 8.4TB to store the full history of the XRP Ledger. You can expect this amount to grow as transaction volume increases across the XRP Ledger network. You can control how much data you keep with the `online_delete` and `advisory_delete` fields. Online deletion enables pruning of `rippled` ledgers from databases without any disruption of service. It only removes records that are not part of the current ledgers. Without online deletion, those databases grow without bounds. Freeing disk space requires stopping the process and manually removing database files. @@ -98,7 +98,7 @@ Any enterprise or carrier-class data center should have substantial network band #### Storage -Ripple recommends estimating storage sizing at roughly 12GB per day of data kept online with NuDB. RocksDB requires around 8GB per day. However, the data per day changes with activity in the network. You should provision extra capacity to prepare for future growth. At the time of writing (2018-10-30), a server with all XRP Ledger history requires 8.4TB. +Ripple recommends estimating storage sizing at roughly 12GB per day of data kept online with NuDB. RocksDB requires around 8GB per day. However, the data per day changes with activity in the network. You should provision extra capacity to prepare for future growth. At the time of writing (2018-10-29), a server with all XRP Ledger history requires 8.4TB.