fix: performance tweak. - #14
Merged
Merged
Conversation
Thanks to: https://github.com/bobbieltd/derogold/commit/81f11906fc78116c442c402b6fa827ec5ce0509a - Exchanges will delist or refuse to list small coins if this shit keeps to be applied - No impact on performance (even quicker better on low end hardware nodes) 256 Mb write is enough. Read buffer is unimportant (it shares with OS cache). Opening files : few hundreds is enough. Back threads 4 (well 4 cores already enough) The original dev put 10 Mb (he was not stupid because it is idiot to put big number there) Turtle dev applied that commit in hurry without much consideration From outside dev Background threads = 10 —> assumption people run CPU with 16 cores or what ? Normally, daemon won’t use many threads but in the worst scenario it will use 10 cores Those config numbers are for worst case. In normal circumstances, daemon utilizes less.
|
128 open files should be plenty for a daemon with a network of this size. It will need to fetch more files in the long run which degrades performance a bit but it will be worth the benefits, which would be:
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Thanks to: https://github.com/bobbieltd/derogold/commit/81f11906fc78116c442c402b6fa827ec5ce0509a
256 Mb write is enough.
Read buffer is unimportant (it shares with OS cache).
Opening files : few hundreds is enough.
Back threads 4 (well 4 cores already enough)
The original dev put 10 Mb (he was not stupid because it is idiot to put big number there)
Turtle dev applied that commit in hurry without much consideration
From outside dev
Background threads = 10 —> assumption people run CPU with 16 cores or what ? Normally,
daemon won’t use many threads but in the worst scenario it will use 10 cores
Those config numbers are for worst case.
In normal circumstances, daemon utilizes less.