No subject

quests per second while Twisted and Cyclone were only handling 400-500 requ=
ests per second.<br>
On loopback from the same m1.small I suspect I was starting to load test th=
e load testers more than the apps but locally all the frameworks were perfo=
rming similarly.<br>
Load testing from another machine to my laptop I was seeing far better perf=
ormance from Twisted and Cyclone, both doing closer to 2k requests per seco=
nd. The other frameworks were only a little quicker but again, there&#39;s =
a chance the machine running the load tests was the bottle neck.<br>

These tests were very unscientifically done but I still wasn&#39;t expectin=
g to see such a big difference between specifically node and Twisted.=A0 50=
0 req/sec is plenty quick for 90% of what I do and of course I know there&#=
39;s so much more to an application than returning hello world but I was wo=
ndering if I was missing some trick to speed Twisted up to get close to the=
 others on EC2.<br>

<br>
</div></div>_______________________________________________<br>
Twisted-Python mailing list<br>
<a href=3D"mailto:Twisted-Python at twistedmatrix.com">Twisted-Python at twistedm=
atrix.com</a><br>
<a href=3D"http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python=
" target=3D"_blank">http://twistedmatrix.com/cgi-bin/mailman/listinfo/twist=
ed-python</a><br>
</blockquote></div><br></div></div>

--001a11c2ffcca0fd4004dae4bb8b--