-
Notifications
You must be signed in to change notification settings - Fork 456
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
crossbeam channel is very slow if restricted to a single core #1031
Labels
Comments
Ahhh, I think I've rediscovered #821 basically! |
Does std mpsc has the same issue? |
cc @ibraheemdev |
I'm working on an idea that should hopefully fix a lot of these related issues. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
TL;DR: restricting a simple essentially sequential ping-pong program to run on a single core reduces performance by an order of magnitude.
Full reproduction here:
https://github.com/matklad/repros/tree/master/ping-pong
The program in question:
As a sanity check, the equivalent Go program (in the repro repo) takes approximately the same time on any number of cores.
The text was updated successfully, but these errors were encountered: