On Fri, 2008-05-30 at 11:19 -0700, Shannon -jj Behrens wrote:
> * There were a couple good points made above about whether to run one > or multiple copies of Paster. It's true that this is one place where > Pylons/Python is very different from Rails/Ruby, as mentioned above. > If you're mostly blocking on IO, then multiple copies won't help much > since multithreaded programs are fine in Python if they're IO > constrained. If you're blocking on CPU, then multiple copies of > Paster running are a really good idea, otherwise the GIL will get in > the way of your making use of multiple cores. I'm curious about this. While it's true that unbounded threading can solve blocking issues, what about thread pools? If you get a large number of simultaneous requests and exhaust either your Pylons thread pool or your SQLAlchemy connection pool (I've been having the latter happen frequently when spammers and bots hit my blog), you get problems. What's the solution besides: 1) increasing thread/connection pool sizes 2) running multiple instances Both of these can provide some temporary relief, but I have to admit that my rather low-traffic blog running into the SA connection pool limits was rather discouraging. Regards, Cliff --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
