-
Notifications
You must be signed in to change notification settings - Fork 23
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
future/async doesn't seem to be async #76
Comments
hi @fkchang. thanks for using angelo! i think the main problem here is using if you try that, it should work the way you expect. lemme know how it works out for you. |
Hi @kenichi Thanks for the quick response. I switched to Celluloid.sleep and I get the same behavior, i.e, after doing 4 requests back to back, watching the output of the angelo program, I see "processing" show up not immediately after 4 times, but about 10 seconds apart, except for the last one. The sleep is to simulate the actual function which is a socket based exchange that could take up to 10 sec, to see whether angelo can meet my response needs. Am I expecting the wrong behavior? |
@fkchang interesting. i used your example with the latest code on master, and i only removed the
as you can see, i did it twice, for a total of ten requests. each time, all 5 returned after 10 seconds:
regarding what the sleep is intending to simulate, an angelo server is a reel server, which is a celluloid::io reactor. if a task blocks on IO, e.g. waiting for a response from a socket, celluloid::io reactor will only work correctly with |
Hi. I'm not sure if I'm using this right, but shouldn't these be handled asyncrhonously?
When I hit it, they are usually serviced 10 sec apart. Occasionally one gets serviced w/in 3 sec.
Perhaps I did not use future correctly? Thank you
The text was updated successfully, but these errors were encountered: