-
Notifications
You must be signed in to change notification settings - Fork 120
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
Open the database in a blocking tokio thread #4821
Comments
I wonder if some of these suggestions can also reduce the opening time |
@conradoplg , there is another ticket to try to apply some of those: #4822 |
This is something we want to do eventually, but it's not urgent. |
We might want to do this usability fix some time during the release candidate series, but it's not a blocker. |
@arya2 it's ok to do the |
Motivation
Zebra can take a long time to re-open the database after the initial sync:
We should do this work in a blocking thread, so it doesn't block the rest of the
tokio
executor.Some RocksDB documentation warns that the first read can also be slow, so we might want to do it in the same blocking call.
Designs
tokio::spawn_blocking()
ortokio::block_in_place()
Related Work
The text was updated successfully, but these errors were encountered: