-
-
Notifications
You must be signed in to change notification settings - Fork 220
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
Celluloid concurrency doesn't parallelize the connection setup #84
Labels
Comments
@mikz Maybe you can help with this? |
I have not worked with Celluloid enough to get this problem. The connect is happening synchronously iirc. |
@mikz I thought that using |
dblock
changed the title
Celluloid concurrency doesn't quite parallelize the connection setup
Celluloid concurrency doesn't parallelize the connection setup
May 2, 2016
Fixed in dblock@e4edaca. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Celluloid creates an
Actor
which then performs a connection. Even if you put this inside aCelluloid.defer
(as I did in dblock/slack-market@3635cdd) it doesn't seem to happen in parallel,build_socket
is blocking. This causes server start with lots of connections to be very slow, as we create TCP connections one-at-a-time.The text was updated successfully, but these errors were encountered: