Devin Torres wrote: > So we're using Pylons and Python in general for our new company > platform. We just bought a server with 4 cores to help us reach our > scalability goals, but there are a few questions I'm interested in > asking the Pylons community. > > I (mostly) understand the nature of "threads" in Python. From my > understanding, the GIL locks the interpreter to executing only one > Python thread at a time, but C modules can take advantage of a Python > application being multithreaded, because they can operate independant > of the GIL. Presumably, this would mean that there is, in fact, a > benefit to using threads in Paste, because most network I/O bound > stuff happens within a C module. > > Given this situation, I believe that despite paste making an effort to > be multithreaded, it would still be advantageous to run a cluster of > four Pylons instances and proxy to these using nginx.
Separate processes is likely to work better. You might find one of the flup forking servers to be better (using fastcgi), though I don't know for sure. That will run each request in its own process, so you'll get multiple processes without the same infrastructure complications of a cluster of servers. I don't think affinity should be that important. Doesn't the OS handle that itself? -- Ian Bicking : [EMAIL PROTECTED] : http://blog.ianbicking.org --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
