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

out of order execution #103

Open
FlorianLudwig opened this issue Jul 8, 2024 · 1 comment
Open

out of order execution #103

FlorianLudwig opened this issue Jul 8, 2024 · 1 comment

Comments

@FlorianLudwig
Copy link

FlorianLudwig commented Jul 8, 2024

When running multiple commands it seems that they have to finish in order.

For example when running:

tokio::time::sleep(tokio::time::Duration::from_millis(100_000)).await;

in the implementation of one of the commands and triggering it, the whole file systems seem to come to a hold.

@Ivanbeethoven
Copy link

I'm not sure if this is correct, but I guess it might be due to the characteristics of Fuse. The design pattern of the Fuse file system is based on an event-loop model, where all requests are scheduled to a single thread and processed sequentially. Achieving 100% parallelism might require you to manually create new threads?

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

2 participants