Yeah. Actually that's the reason I refactored txRiak to use Agent instead of HTTPClient, so it could take advantage of pooling when that comes down the pike for Agent (well that and HTTP 1.1 support).
I guess I'll just throttle down the load rate. Thank you for your help. -J On Fri, Mar 4, 2011 at 12:40 PM, <exar...@twistedmatrix.com> wrote: > On 05:09 pm, jasonjwwilli...@gmail.com wrote: >>Actually, I think the TIME_WAIT is the problem. It's what I see in >>netstat, and the Agent requests are fired sequentially via yield inside >>a for loop (inlineCallbacks). So they shouldn't be running in parallel. >> >>The use case here is loading a Riak server with keys to prepare for a >>test. There's not a real way to get around sending one POST per key. >> >>How would I set the timeout value in Twisted? Or do I have to modify >>the timeout/keepalive systemwide in /proc? > > As far as I know, there are only system-wide settings for this value on > all the major platforms. > > It seems like you'll be happiest using persistent connections, though, > once Agent actually offers those. > > Jean-Paul > > _______________________________________________ > Twisted-Python mailing list > Twisted-Python@twistedmatrix.com > http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python > _______________________________________________ Twisted-Python mailing list Twisted-Python@twistedmatrix.com http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python
