-
Notifications
You must be signed in to change notification settings - Fork 452
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
Stop reading bootstrap SQL dump at each startup #4862
Comments
We could turn this into a REST endpoint and have the GUI control when to perform the bootstrap SQL statement. |
I suppose we will address this issue after the 7.5 release? |
For 7.5, we just disabled reading SQL from the bootstrap file. We can solve it later in 7.5.x or 7.6 series. |
By, Trustchain! |
TrustChain is not entirely gone yet and the bootstrap code is still there. We left it in since it will trigger bandwidth payouts which will make sure that you are connected to other users. The content in the bootstrap file, however, is currently not being parsed. There are plans to address this soonish. |
🤷 |
This code seems to have been removed now making this issue no longer relevant. |
Currently, we fully read and execute the bootstrap SQL dump at each startup. This increases the startup time (which is critical for a torrent client). Also, it puts unnecessary load on TrustChain SQL engine, which can potentially slow down other TrustChain-related startup sequences.
Instead, we should detect if the current bootstrap file has already been processed before, and only load the SQL dump if necessary.
The text was updated successfully, but these errors were encountered: