1 point by tzury 10 months ago | link
cached 4 months ago

71 points by roder 10 months ago | link
cached 4 months ago

50 points by roder 10 months ago | link
cached 4 months ago

-3 points by lamby 10 months ago | link | top
cached 4 months ago
Needs more tornado. Or, err, twisted.web.

Tornado on Twisted (github.com)
65 points by webology 10 months ago | link
cached 4 months ago

7 points by philjackson 10 months ago | link | top
cached 4 months ago
Am I mis-reading that graph or is it the case that twisted.web handles half the concurrent connections that tornado does /and/ more slowly? Is it possible that twisted performing "almost as well" as tornado might be exaggerated?

1 point by andrewvc 10 months ago | link | top
cached 4 months ago
Well, if this benchmark from yesterday is accurate, then Twisted can't handle as many concurrent connections as Tornado. I'd say that's a good reason not to use Twisted.

http://www.apparatusproject.org/blog/2009/09/twisted-web-vs-...


6 points by roder 10 months ago | link | parent | top
cached 4 months ago
I did split the machines. The driver (the one running the test) machine is completely different than the webserver running twisted.web or tornado.

3 points by karanbhangui 9 months ago | link | top
cached 3 months ago
I'm curious how this compares to twisted.web/tornado in terms of use case (friendfeed type sites). Can anyone quickly explain this to me? Thanks!

1 point by dws 10 months ago | link | parent | top
cached 4 months ago
How does tornado on twisted perform relative to tornado?