On Tue, Dec 15, 2009 at 5:18 PM, Mike Orr <sluggos...@gmail.com> wrote: > On Tue, Dec 15, 2009 at 2:39 PM, Joan Miller <pelok...@gmail.com> wrote: >> Pylons is a great project, thanks! But I'm supposed that it would be >> faster if it were ready for concurrency. >> >> Today is not necessary to use Twisted; it's great, but forces you into >> callback hell. In change, pyev [1] is a great solution. >> >> [1] http://code.google.com/p/pyev/
One other issue is that the thread overhead is not usually the bottleneck in a WSGI application. Database access has a much bigger impact on performance. If you need to handle thousands of simultaneous requests, you probably need multiple servers anyway. Offloading static files to Apache or Nginx or a proxy server is another way to boost performance and keep the thread count down in Pylons. You can also try the CherryPy server, which although also threaded, is supposed to have better performance than Paste's HTTP sever. Also, make sure you really need the capacity. Many people overestimate the number of simultaneous requests they will have. A moderately large (but not huge) site may get only four requests per minute. -- Mike Orr <sluggos...@gmail.com> -- You received this message because you are subscribed to the Google Groups "pylons-devel" group. To post to this group, send email to pylons-de...@googlegroups.com. To unsubscribe from this group, send email to pylons-devel+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/pylons-devel?hl=en.
