-
Notifications
You must be signed in to change notification settings - Fork 721
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
[FR] - Faster verification of on-disk cache #5500
Comments
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 120 days. |
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 120 days. |
Maybe this could be resolved by allowing I heard somewhere that the node uses by default only two cores. |
Thank you, @ch1bo! For me, specifically, I don't think I am using Docker, so would it be possible for me to just specify -N (or other options) somewhere in a config file? Again, specifically for me, Cardano-node seems to actually be started by Daedalus Wallet on Linux. |
Update from my end: Having seen what I reported with cardano-node via Daedalus, actually getting cardano-node to pick up The relevant part for this thread is that not only does that speed up things considerably, but it also seems to work around another problem I had with cardano-node seemingly losing connection to mainnet, necessitating a process restart. Whether that is a function of this being run by Daedalus, however, is unknown to me. Hence, I shall take my findings up with the Daedalus developers, and leave it up to to the cardano-node developers to decide upon whether to implement one or more of my suggestions - for them, it would probably still be relevant, though, to promote RTS options somehow. |
Internal/External
External
Area
Other
Describe the feature you'd like
Drastic reduction of time needed for verification of on-disk blockchain state
Describe alternatives you've considered
Additional context / screenshots
For quite some time, using Daedalus, that Electron client will frequently revert back to the semblance of the start-up screen, with the point "Verifying on-disk blockchain state" showing 99.something percent, "Replaying ledger from on-disk blockchain" showing a low percentage, and "Syncing blockchain" showing 0.00%.
Remedy is restart of cardano-node.
This will, of course, trigger a verification of the on-disk blockchain state, which, on my system, pegs a single CPU core to 100%, but only reads from disk in "bursts" of between ~5MB/s to ~35MB/s, and the process takes several hours to complete.
Since a single core is utilised to 100%, and disk read speeds are low, it must be possible to parallelise parts of whatever it does, and it should also be possible to avoid actually reading the whole shebang on each (re-) start.
The text was updated successfully, but these errors were encountered: