4 ms·
Summary: * Mean response time -- Twisted.Web better than Tornado Average performances for Concurrent request: * @100 -- TW:Tor::0.50s:0.70s . TW better
by FraaJad 17y ago
Summary:
* Mean response time -- Twisted.Web better than Tornado
Average performances for Concurrent request:
* @100 -- TW:Tor::0.50s:0.70s . TW better than Tor
* @500 -- TW:TOr:: 3s:3.5s . TW slightly better than Tor
* @1000 -- TW:Tor:: 5s:6.5s . TW better than Tor
- deleted 17y ago[deleted]
- jsdalton 17y agoThanks, this is helpful. Not to be a stickler, but two things on your summary: * Where are you getting your estimates from? The numbers on the spreadsheet in the article do not match your rounded summaries. * Twisted is faster at the same proportions for all the concurrent request numbers. Your summary makes it sounds like it's only slightly better at 500, but significantly better at all other request numbers. In fact, it's about 120% faster across the board. Since yours is the top rated comment, I think you should ensure that it's accurate.
- ncarlson 17y agoThis comparison makes me wonder what the upper limit is for python-based server performance. I wonder where the main bottleneck lies.
- moe 17y agoExecutive summary: Ignore this "benchmark", the author simply doesn't have a remote clue what he is doing. 500ms Mean Response Time at 100 concurrent requests, are you kidding? Did you run the "benchmark" over a 56k modem? For the record, one would expect sub-100ms response times under that load, even on modest hardware.
- roder 17y agowow... The test was run on two VMs on the Rackspace cloud using the public IP addresses.