On Aug 24, 2007, at 4:41 AM, Pekka Jääskeläinen wrote:
> Hello, > > In our new project we want to implement the web application from > the beginning to be > easily scalable to 1) multiple cores (on the same server) and to 2) > multiple separate servers. > > Due to the infamous GIL ruining multithreading scalability of > Python, the only sensible way to > implement both 1) and 2) seems to be to run multiple instances of > the server (we plan to > use the Paster to serve the app) and use a separate load-balancer > (possibly some Apache mod... > any recommendations?) to redirect requests to each of the server > instances running either on the > same machine (to take advantage of 1) or to separate servers (to > implement 2). Apache 2.2 has a mod_proxy_balancer. If performance is a concern, you should go with the CherryPy WSGI server. use = egg:PasteScript#cherrypy instead of use egg:Paste#httpserver > > Of course, in this setup there's no real difference between 1) and > 2) which is kind of nice. > > However, we started to think the practical issues with this in > Pylons. In principle, making this work > reliably means to distribute the session data so all server > processes can access each session's data. > For this we plan to store the session data to the database and > reduce its overhead using memcached. Beaker has support for using a database or a memcached backend, though the docs on how to do this seem to be currently lacking. -- Philip Jenvey --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
