-
Notifications
You must be signed in to change notification settings - Fork 649
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merge release back to develop for doc update #1378
Conversation
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.
add new doc portals to readme
Add disk space requirements to readme
README.md
Outdated
@@ -76,7 +78,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 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think these numbers are wrong. SSD is only required for ES, for normal nodes a classic HD is sufficient.
Blockchain size is currently about 33G, don't know why you specify different HD sizes. Logfiles?
Minimal node should work in 4 GB I think (no history).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is recommended sizes.
Even for ES node HD will do the job but slower(there are public mainnet elastic nodes with HD).
Eventually we will suggest SSD everywhere to make a sync in a reasonable time. Right now i think we can change to HDD Default and Minimal. In minimal we can change back to 4G in RAM.
Disk size of 80G is ok if the chain is 33G, this should be the size of disk someone should purchase to run it, so considering OS and other tools 80G sounds reasonable or at least 60G.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We can also add block producer node to the table.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@oxarbitrage is right !
We need both API and Witness nodes requirements information IMHO, would be very helpful really !
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Block producers and seed nodes can run minimal configuration. Witness plugin does not require meaningful additional RAM.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sync is bounded by network, not by HD speed. IMO. No need to recommend SSD.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
change back to HDD and 4G RAM for minimal
I think full nodes should be run on SSD to increase startup/shutdown speed. By the way, I've wrote a few commit comments about reasoning when adding the numbers, although the extra spaces are arbitrary.
|
merge release to patch-4
update date of requirements table
No description provided.