Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

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

Opendal support sync read/write API #40

Closed
sundy-li opened this issue Feb 21, 2022 · 2 comments
Closed

Opendal support sync read/write API #40

sundy-li opened this issue Feb 21, 2022 · 2 comments

Comments

@sundy-li
Copy link
Contributor

For local fs, we can switch into sync read/write API to improve the performance

@Xuanwo
Copy link
Member

Xuanwo commented Feb 22, 2022

tokio is much slower

  • fs is based on tokio::fs
  • bfs is a simple wrapper by blocking

On NVMe SSD

meAwh2bpZX

On tmpfs (in memory)

image

@Xuanwo
Copy link
Member

Xuanwo commented Feb 22, 2022

So the conclusion is:

  • tokio::fs is so slow that maybe we should not use it for our fs backend.
  • It's worth to provide a sync version API
  • We need to develop a real async io fs backend based on aio or io_uring: see Async fs support #19

@apache apache locked and limited conversation to collaborators Feb 25, 2022
@Xuanwo Xuanwo converted this issue into discussion #68 Feb 25, 2022

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants