<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On Oct 13, 2009, at 10:44 PM, Daniel Griffin wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">Hi,<br><br>I am new to twisted and have been having trouble finding out information about twisted's performance. I have a fairly simple setup where I need to open a bunch of TCP connections that last for varying amounts of time but dont do much. I have tried using threads(got GILed to death) and Processes(even worse). Now I am looking at either making a system to start the connection and send info to have the remote point "phone home" when its done, then closing the connection or using something like Twisted. <br>
<br>my socket conversation:<br><span class="Apple-tab-span" style="white-space:pre"> </span>my app -> send a message that triggers an action on the other end<br></blockquote><blockquote type="cite"><span class="Apple-tab-span" style="white-space:pre"> </span>other end -> recv's message does action(can take any amount of time)<br></blockquote><blockquote type="cite"><span class="Apple-tab-span" style="white-space:pre"> </span>other end - > sends results back to my app<br></blockquote><br><div><a href="http://twistedmatrix.com/projects/core/documentation/howto/clients.html">Twisted Documentation: Writing Clients</a></div><div><br></div>I would suggest deferring worrying at this point. (;-b).</div><div><br></div><div>Twisted can almost certainly handle it.</div><div><br></div><div>Do the simplest thing possible, see how it performs, then worry as necessary.</div><div><br></div><div>S</div><div><br></div></body></html>