Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Switch from block_in_place to spawn_blocking for async operations #9

Open
neysofu opened this issue May 22, 2024 · 1 comment
Open

Switch from block_in_place to spawn_blocking for async operations #9

neysofu opened this issue May 22, 2024 · 1 comment

Comments

@neysofu
Copy link
Member

neysofu commented May 22, 2024

We currently use tokio::task::block_in_place for async operations within Rockbound, but we'd probably like to switch to spawn_blocking. spawn_blocking has some performance benefits and, most importantly, doesn't abort in case of panics but instead recovers from them.
@neysofu
Copy link
Member Author

neysofu commented May 22, 2024

When this is solved, I believe we can remove all (flavor = "multi_thread") attributes from Rockbound as well as sovereign-sdk.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@neysofu