-
-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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
bump lmdb sync threshold for performance #8839
Conversation
Force sync every 100k blocks instead of every 1k blocks. Bumping this value is reported to make a big difference in sync performance, eg: monero-project#8189
Is it known why Windows corrupts more often for unsynced writes than other operating systems? |
@jeffro256 many reasons; primarily it's simply a more unstable OS and prone to spontaneous OS crashes. Also its users are generally less sophisticated, and will more often e.g. disconnect an external drive without safely unmounting/ejecting it first. |
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.
so i just like to click through the PRs when the list goes up on IRC and this caught my eye but its me so you know....
@@ -576,7 +576,11 @@ namespace cryptonote | |||
else if(options[0] == "fastest") | |||
{ | |||
db_flags = DBF_FASTEST; | |||
#ifdef _WIN32 |
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.
so its me and I really don't know what im doin..
but does PR #8848 do something to this ifdef _win32 thing? or is it still fine and dandy somehow.
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.
unrelated, _WIN32 is always available
rightio. |
wait i think i hit a wrong button. sorry. i'll move away from the keyboard now. |
Force sync every 100k blocks instead of every 1k blocks. Bumping this value is reported to make a big difference in sync performance, eg: #8189