From 8b0ace5420142fee842b7e5790a0fe7a6046561b Mon Sep 17 00:00:00 2001 From: Alfredo Garcia Date: Tue, 9 Oct 2018 20:11:40 -0300 Subject: [PATCH 1/7] add new doc portals to readme replace https://github.com/bitshares/bitshares-core/pull/1358 --- README.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/README.md b/README.md index fd56290d3b..d58cee3fbd 100644 --- a/README.md +++ b/README.md @@ -20,6 +20,8 @@ The web wallet is [BitShares UI](https://github.com/bitshares/bitshares-ui). Visit [BitShares.org](https://bitshares.org/) to learn about BitShares and join the community at [BitSharesTalk.org](https://bitsharestalk.org/). +Information for developers can be found in the [Bitshares Developer Portal](https://dev.bitshares.works/). Users interested in how bitshares works can go the [BitShares Documentation](https://how.bitshares.works/) site. + Getting Started --------------- Build instructions and additional documentation are available in the From cd8d11157e3905b34a574024b38da0a29b866cb8 Mon Sep 17 00:00:00 2001 From: Alfredo Garcia Date: Tue, 9 Oct 2018 21:09:50 -0300 Subject: [PATCH 2/7] fix sentence --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index d58cee3fbd..308669159a 100644 --- a/README.md +++ b/README.md @@ -20,7 +20,7 @@ The web wallet is [BitShares UI](https://github.com/bitshares/bitshares-ui). Visit [BitShares.org](https://bitshares.org/) to learn about BitShares and join the community at [BitSharesTalk.org](https://bitsharestalk.org/). -Information for developers can be found in the [Bitshares Developer Portal](https://dev.bitshares.works/). Users interested in how bitshares works can go the [BitShares Documentation](https://how.bitshares.works/) site. +Information for developers can be found in the [Bitshares Developer Portal](https://dev.bitshares.works/). Users interested in how bitshares works can go to the [BitShares Documentation](https://how.bitshares.works/) site. Getting Started --------------- From 8d6ba356a8100e450b0ef93cfb00d886ad0d3d62 Mon Sep 17 00:00:00 2001 From: Abit Date: Mon, 15 Oct 2018 11:51:58 +0200 Subject: [PATCH 3/7] Add disk space requirements to readme On 2018-10-15, * block file (plus index) is around 35G; * on-disk object database is around 1/5 of RAM used; * default p2p logs are around 12G (level = warn, keep 7 days); * console logs and rpc logs are relatively small. --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index fd56290d3b..280d60b089 100644 --- a/README.md +++ b/README.md @@ -76,7 +76,7 @@ In order to run a full node with all the account history you need to remove `par | Default | Full | Minimal | ElasticSearch | --- | --- | --- | --- -| 16G RAM | 120G RAM | 4G RAM | 500G SSD HD, 32G RAM +| 100G SSD, 16G RAM | 200G SSD, 120G RAM | 80G SSD, 8G RAM | 500G SSD, 32G RAM After starting the witness node again, in a separate terminal you can run: From 5a83944908cc50218864846cace5a18b9f662105 Mon Sep 17 00:00:00 2001 From: Alfredo Garcia Date: Mon, 15 Oct 2018 09:24:45 -0300 Subject: [PATCH 4/7] update date of requirements table --- README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index 255c9fb468..0f1b0122c3 100644 --- a/README.md +++ b/README.md @@ -73,8 +73,8 @@ the blockchain. After syncing, you can exit the node using Ctrl+C and setup the rpc-endpoint = 127.0.0.1:8090 -**IMPORTANT:** By default the witness node will start in reduced memory ram mode by using some of the commands detailed in [Memory reduction for nodes](https://github.com/bitshares/bitshares-core/wiki/Memory-reduction-for-nodes). -In order to run a full node with all the account history you need to remove `partial-operations` and `max-ops-per-account` from your config file. Please note that currently(2018-07-02) a full node will need more than 100GB of RAM to operate and required memory is growing fast. Consider the following table before running a node: +**IMPORTANT:** By default the witness node will start in reduced memory mode by using some of the commands detailed in [Memory reduction for nodes](https://github.com/bitshares/bitshares-core/wiki/Memory-reduction-for-nodes). +In order to run a full node with all the account history you need to remove `partial-operations` and `max-ops-per-account` from your config file. Please note that currently(2018-10-15) a full node will need more than 120GB of RAM to operate and required memory is growing fast. Consider the following table before running a node: | Default | Full | Minimal | ElasticSearch | --- | --- | --- | --- From f0d88ff34efe44bf6400ae9ef2cce27819a831c2 Mon Sep 17 00:00:00 2001 From: Alfredo Garcia Date: Mon, 15 Oct 2018 14:12:30 -0300 Subject: [PATCH 5/7] change back to HDD and 4G Ram for minimal --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 255c9fb468..35e18cff73 100644 --- a/README.md +++ b/README.md @@ -78,7 +78,7 @@ In order to run a full node with all the account history you need to remove `par | Default | Full | Minimal | ElasticSearch | --- | --- | --- | --- -| 100G SSD, 16G RAM | 200G SSD, 120G RAM | 80G SSD, 8G RAM | 500G SSD, 32G RAM +| 100G HDD, 16G RAM | 200G HDD, 120G RAM | 80G HDD, 4G RAM | 500G SSD, 32G RAM After starting the witness node again, in a separate terminal you can run: From 5c420208d596eed88c8fb010b9721a3da280db98 Mon Sep 17 00:00:00 2001 From: Alfredo Garcia Date: Tue, 16 Oct 2018 18:38:06 -0300 Subject: [PATCH 6/7] make clear table is minimal requirements --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 0f1b0122c3..333b540ca5 100644 --- a/README.md +++ b/README.md @@ -74,7 +74,7 @@ the blockchain. After syncing, you can exit the node using Ctrl+C and setup the rpc-endpoint = 127.0.0.1:8090 **IMPORTANT:** By default the witness node will start in reduced memory mode by using some of the commands detailed in [Memory reduction for nodes](https://github.com/bitshares/bitshares-core/wiki/Memory-reduction-for-nodes). -In order to run a full node with all the account history you need to remove `partial-operations` and `max-ops-per-account` from your config file. Please note that currently(2018-10-15) a full node will need more than 120GB of RAM to operate and required memory is growing fast. Consider the following table before running a node: +In order to run a full node with all the account history you need to remove `partial-operations` and `max-ops-per-account` from your config file. Please note that currently(2018-10-15) a full node will need more than 120GB of RAM to operate and required memory is growing fast. Consider the following table as minimal requirements before running a node: | Default | Full | Minimal | ElasticSearch | --- | --- | --- | --- From 5959f70308fe1fef07c26c47c36098128111176c Mon Sep 17 00:00:00 2001 From: Alfredo Garcia Date: Wed, 17 Oct 2018 11:36:37 -0300 Subject: [PATCH 7/7] change to 160G of ram for full node --- README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index 1f5b2d70c2..a516790596 100644 --- a/README.md +++ b/README.md @@ -74,11 +74,11 @@ the blockchain. After syncing, you can exit the node using Ctrl+C and setup the rpc-endpoint = 127.0.0.1:8090 **IMPORTANT:** By default the witness node will start in reduced memory mode by using some of the commands detailed in [Memory reduction for nodes](https://github.com/bitshares/bitshares-core/wiki/Memory-reduction-for-nodes). -In order to run a full node with all the account history you need to remove `partial-operations` and `max-ops-per-account` from your config file. Please note that currently(2018-10-15) a full node will need more than 120GB of RAM to operate and required memory is growing fast. Consider the following table as minimal requirements before running a node: +In order to run a full node with all the account history you need to remove `partial-operations` and `max-ops-per-account` from your config file. Please note that currently(2018-10-17) a full node will need more than 160GB of RAM to operate and required memory is growing fast. Consider the following table as minimal requirements before running a node: | Default | Full | Minimal | ElasticSearch | --- | --- | --- | --- -| 100G HDD, 16G RAM | 200G HDD, 120G RAM | 80G HDD, 4G RAM | 500G SSD, 32G RAM +| 100G HDD, 16G RAM | 200G HDD, 160G RAM | 80G HDD, 4G RAM | 500G SSD, 32G RAM After starting the witness node again, in a separate terminal you can run: