-
-
Notifications
You must be signed in to change notification settings - Fork 9
Use async-channel or flume #18
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
Labels
enhancement
New feature or request
Comments
Certainly! Sluice was initially written before either async-channel or flume were created, but those are both better options than futures-channel today. I usually prefer async-channel since flume has a heavier dependency tree. |
sagebind
added a commit
that referenced
this issue
Aug 15, 2021
Switch the underlying channel implementation from futures-channel to async-channel, since the former has been shown to fall behind on performance metrics. In addition, crates from the futures project tend to have slower compile times compared to some alternatives. Fixes #18.
sagebind
added a commit
that referenced
this issue
Aug 15, 2021
Switch the underlying channel implementation from futures-channel to async-channel, since the former has been shown to fall behind on performance metrics. In addition, crates from the futures project tend to have slower compile times compared to some alternatives. Fixes #18.
Thanks for the suggestion! Sluice now uses async-channel under the hood in version 0.5.5! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
futures-channel
is known to be of poor performance; would usingasync-channel
orflume
be considered?The text was updated successfully, but these errors were encountered: