-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Make the transaction-cache initialization faster #5355
Comments
Looking forward for its implementation. |
@lurais Sounds great. I am not sure if it's faster to start. but I guess maybe if you implement it. |
@halibobo1205 yes, a pr about the solution will be proposed subsequently。 |
Hi |
@Shuo613 Hello, do you have any questions ? |
@halibobo1205 A draft of that is here : #5377 |
兄弟哪裡 |
English please dear, and also please do not post worthless content |
@halibobo1205 Can you take care of the development of this feature? |
@lvs007 We're ready for review #5394 . Expected to take less than 1s |
If it goes from 20+ seconds down to about 1 second, that would be a big improvement; a very good improvement. |
Rationale
At present, it takes about 35s to start the node, and it takes 25 to 30s to load the transaction cache in the node start period.
And the bloom filter is used as the transaction cache actually.
So it is expected to shorten the node start time by loading the bloom filter faster.
Why should this feature exist?
1.To make the node start faster.
Implementation
1.The node writes the bloom filter to the disk when the kill -15 signal is received.
2.Load the bloom filter into the ram if the bloom filter file is existed and can be opened normally,
or build the transaction cache from recent 65536 blocks like before.
Additional information
kill -15 is required
Related PRs
The text was updated successfully, but these errors were encountered: