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.

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

io_uring #11

Open
Demi-Marie opened this issue Jul 8, 2020 · 4 comments
Open

io_uring #11

Demi-Marie opened this issue Jul 8, 2020 · 4 comments

Comments

@Demi-Marie
Copy link

This is a significant performance win.

@arkpar
Copy link
Member

arkpar commented Jul 8, 2020

Are there any benchmarks that show significant performance gains for sync reads over memory mapped IO?

@Demi-Marie
Copy link
Author

io_uring is entirely asynchronous.

@arkpar
Copy link
Member

arkpar commented Jul 8, 2020

This library provide synchronous API for reads. That's not going to change to async since we can't do async IO from WASM.
That said io_uring might still be faster than traditional IO when used in synchronous mode (that is waiting for the result after each operation). As it does not require a kernel call. It is not clear though if it will be faster than memory mapped IO.

As for commits, these are asynchronous already and are performed in the background. Commit performance is not that critical for substrate, since it works in parallel with block import.

@ordian
Copy link
Member

ordian commented Nov 27, 2020

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants