is the django fastcgi startup comment I'm testing with. If I then run a benchmark test to load the server like so:
ab -n1000 -c15 -H 'Host: www.example.com' http://127.0.0.1/
With nginx running on port 80 in a fastcgi configuration to port 8001, a few requests will go through successfully, but then eventually the fastcgi process segfaults. No stack trace.
I'm hoping to use the threaded model in the future as it should use less memory than the prefork. Anyhow, the only reason I can think of as to why this is bugging out is to do with threading issues to do with the Python GIL (http://docs.python.org/c-api/init.html#thread-state-and-the-global-interpreter-lock)
Thoughts? Can I provide further information to you? Feel free to email me. Thank you!