Hi all, I'm building an HTTP benchmarker/load-tester using AHC ( https://github.com/andrewvc/engulf ) and am wondering what the best AHC configuration for me to use would be.In general AHC works great, however, when I try and hit a server with keep-alive disabled, it seems to choke up. Running only 4 concurrent requests/second against an nginx server with keep-alive disabled the process locks up with no error messages. Enabling keep-alive prevents this completely.Does anyone have any ideas what the issue could be? I would guess that it's file descriptor related, but I've tried upping available FDs with ulimit without luck.
--
You received this message because you are subscribed to the Google Groups "asynchttpclient" group.
To view this discussion on the web visit https://groups.google.com/d/msg/asynchttpclient/-/9WS3cbqO98MJ.
To post to this group, send email to asyncht...@googlegroups.com.
To unsubscribe from this group, send email to asynchttpclie...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/asynchttpclient?hl=en.
I'd probably use it if it weren't for half the fact being that engulf
is just really fun to hack on. I love networks, systems, clojure, and
performance problems, so as cool as gatling is, it doesn't fit the
bill personally :).
I'm wondering, however, Stephane, if you've hit this issue at all?
With 4 concurrent requests, and keep alive disabled, AHC seems to
choke after the 16,000th request or so on my OSX box hitting nginx
locally. Have you seen anything like this? I feel like there's some
kind of allocation bug that must be going wrong no?
-- Andrew
April 20, 2012 4:48 PM
Hey Stephane, thanks for the link. Gatling looks like a really cool project!
I'd probably use it if it weren't for half the fact being that engulf
is just really fun to hack on. I love networks, systems, clojure, and
performance problems, so as cool as gatling is, it doesn't fit the
bill personally :).
I'm wondering, however, Stephane, if you've hit this issue at all?
With 4 concurrent requests, and keep alive disabled, AHC seems to
choke after the 16,000th request or so on my OSX box hitting nginx
locally. Have you seen anything like this? I feel like there's some
kind of allocation bug that must be going wrong no?
-- Andrew
On Thu, Apr 19, 2012 at 10:37 PM, Stéphane Landelle
April 20, 2012 7:37 AM
Hi Andrew,Are you sure you want to build your own project?Competition is a good thing, but we've been building Gatling for 1 year now and it uses AHC:Cheers,Stephane
--
You received this message because you are subscribed to the Google Groups "asynchttpclient" group.
To post to this group, send email to asyncht...@googlegroups.com.
To unsubscribe from this group, send email to asynchttpclie...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/asynchttpclient?hl=en.
April 20, 2012 6:07 AM
Hubert, that's exactly the case, no keep alive is used. I meant to say that with only 4 simultaneous clients no more than 4 FDs should be consumed at any one time correct? netstat shows that only 4 are used simultaneously.
> To post to this group, send email to asynchttpclient@googlegroups.com.
> To unsubscribe from this group, send email to asynchttpclient+unsubscribe@googlegroups.com.
-+ Tatu +-
--
You received this message because you are subscribed to the Google Groups "asynchttpclient" group.
To post to this group, send email to asyncht...@googlegroups.com.
To unsubscribe from this group, send email to asynchttpclie...@googlegroups.com.