3 ms·
Through forking + gevent and then sleeping in each request handler. Of course it measures nothing other than a whole bunch of while loops running in one fork pe
by notzorbo3 10y ago
Through forking + gevent and then sleeping in each request handler. Of course it measures nothing other than a whole bunch of while loops running in one fork per CPU waiting for just about nothing. In other words, I'm benchmarking "how much memory do I have", which is pointless. But it sure does scale!
- lessclue 10y agoTCP handshakes->HTTP parsing->Sleep->Response writing. Can the overhead added by these (and more) possibly produce 24+ million requests / sec on a commodity machine? Could you share some examples or snippets?
- mozumder 10y agothe way most python web apps work is they don't do the TCP handshake & http parsing, and leave that up to the front-end web server (nginx/apache/etc). Python only comes in via a fastcgi or wsgi proxy.