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? -J Sent via iPhone Is your e-mail Premiere? On Mar 4, 2011, at 6:53, Itamar Turner-Trauring <ita...@itamarst.org> wrote: > On Fri, 2011-03-04 at 13:33 +0000, exar...@twistedmatrix.com wrote: > >> It's worse than just "in parallel". After the connection closes, it >> moves to TIME_WAIT for two minutes. These count towards the limit as >> well. > > Oh right: > http://twistedmatrix.com/trac/ticket/1288 > > You could probably set that yourself with a little hacking until that > ticket is fixed. > > > _______________________________________________ > 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
