-
Notifications
You must be signed in to change notification settings - Fork 416
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
concurrent-ruby-edge Channel.select consumes full(single core) cpu #883
Comments
adityacs
changed the title
concurrent-ruby-edge Channel.select consumes full cpu on single core system
concurrent-ruby-edge Channel.select consumes full(single core) cpu
Aug 30, 2020
It is Ruby, not go, so it is not possible to push from another thread to the current one, like it is implemented in go's As the result you can only pull, which this Adding |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I am running this simple code and I see that
select
is not blocking on thechannels
and instead alwayslooping
which consumes full(single core) CPU.The text was updated successfully, but these errors were encountered: