Skip to content
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

update date of requirements table #1379

Merged
merged 4 commits into from
Oct 17, 2018
Merged

update date of requirements table #1379

merged 4 commits into from
Oct 17, 2018

Conversation

oxarbitrage
Copy link
Member

related to #1376

@abitmore
Copy link
Member

We'd better get an accurate number. Who have a full node running?

@oxarbitrage oxarbitrage added this to the 201810 - Feature Release milestone Oct 16, 2018
@pmconrad
Copy link
Contributor

If we can't get an up-to-date number we should not bump the date.

@oxarbitrage
Copy link
Member Author

I was able to get some input from @dls-cipher in the bitshares nodes admin channel in telegram.

134.1GB was June metrics, right now the estimate of real RAM is of 160G however a full node according to his experience will synchronize and run fine for a while with 128G RAM and 200G of SSD.

I suppose some of the SSD is used as RAM at some point and will be good enough for us by now.

@pmconrad
Copy link
Contributor

SSD isn't used as RAM. Swapspace at most, but that's still orders of magnitude slower.
I think we should document 160G for the full node. It's not a recommended setup anyway.

I have also experienced that a long-running node uses much more RAM than right after restart, i. e. with the same database size. Either that's due to fragmentation, or we have leaks.

@oxarbitrage oxarbitrage merged commit a0f098e into release Oct 17, 2018
@abitmore abitmore deleted the oxarbitrage-patch-4 branch October 20, 2018 09:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants