Forwarding as he replied directly to me ^^ Yes, serving static files using Paster takes away threads that are better used by serving dynamic content. That is why I was suggesting to move static files to nginx or anything else.
---------- Forwarded message ---------- From: Rotem Tamir <[email protected]> Date: Mon, Dec 12, 2011 at 2:24 PM Subject: Re: Tg2.1 scaling very slow To: Alessandro Molina <[email protected]> Hi everyone, just wanted to update that the issue was partially related to TG. I was serving some of my static assets thru paster which was taking up a lot of resources. I ended up serving them thru amazon S3 which is blazingly fast. On Oct 11, 11:55 am, Alessandro Molina <[email protected]> wrote: > On Sun, Oct 9, 2011 at 7:40 PM,RotemTamir <[email protected]> wrote: > > Hi all > > > I'm currently moving a TG2.1 app to production and have been doing > > some load testing. > > > I have 10 Instances of the app running behind an nginx server using > > reverse proxy technique. > > > When I reach about 50-60 concurrent users the application becomes > > incredibly slow, responding sometimes at 40-50 seconds response time. > > - Check that you have enough available connections to the database > (both the db server and sqlalchemy have a maximum pool size usually) > - If you are using paster, don't use paster > - Prefer spawning multiple processes and less threads if you are > deploying with mod_wsgi and have enough ram > - Disable template reloading in app_cfg.py > - Move the static files to nginx, they consume slots that can be used > by the dynamic content related requests > - 40-50 seconds is HUGE, it is probably not related to tg app itself, > but some deployment issues or db issues. -- You received this message because you are subscribed to the Google Groups "TurboGears" 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/turbogears?hl=en.
