Hi! New here. I've been trying various ways of deploying Pylons apps for production and so far have a problem with each. Can someone help with paste.httpserver and/or flup_fcgi?
With paste.httpserver (as well as the alternate wsgiutils HTTP server), I had problems during load testing with a simple non-database app. I use ab (apache bench) for this and noticed the server was able to handle concurrency of only about 10 before error responses started creeping in. By -c 50 (behind lighttpd proxy) or by -c 12 (on its own) it was knocked over. Since I've read about people using this approach in production, there must be something anomalous going on. What should I look at first? I tried to up the thread count using what limited docs I could find, but could not find the magic config formula. (Putting threadpool_workers = 30 under [server:main] did not seem to work, as log messages still referenced 10 threads, the default). With flup_fcgi behind lighttpd, performance is great, with consistent response times and no errors up to concurrency of about 240 (around 250 I run out of sockets). But lighttpd's mod_fastcgi fills in SCRIPT_NAME and PATH_INFO in a way completely contrary to what Routes expects. I can give config examples if necessary but maybe someone is already familiar with this. Is there a good way to compensate and make Routes work? Can't find anything in the lighttpd docs, Pylonshq docs, or Routes source code. I don't want to use middleware in the app itself as that would tie the app to a particular server type, though I suppose I could make it configurable if necessary. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/pylons-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
