Name: Anonymous 2010-12-12 15:10
I want a HTTP server that does something very simple:
1) Receive request
2) Respond with a tiny file; close HTTP connection
3) Parse the request data and persist it
The server must perform under EXTREME ENTERPRISE LOADS. How should I proceed?
Everybody talks about non-blocking I/O and stuff, but none of the frameworks I've seen (eventlet, gevent, EventMachine) seem to suit my need. In all of them the requests/sec go down as soon as I do any real work, and it's impossible to answer the requests before handling the data. Is this so absurd? The clients don't care what they get back; the important thing for me is that no request gets lost.
Should I just use regular threads? Help me, /prog/.
1) Receive request
2) Respond with a tiny file; close HTTP connection
3) Parse the request data and persist it
The server must perform under EXTREME ENTERPRISE LOADS. How should I proceed?
Everybody talks about non-blocking I/O and stuff, but none of the frameworks I've seen (eventlet, gevent, EventMachine) seem to suit my need. In all of them the requests/sec go down as soon as I do any real work, and it's impossible to answer the requests before handling the data. Is this so absurd? The clients don't care what they get back; the important thing for me is that no request gets lost.
Should I just use regular threads? Help me, /prog/.