If you are on postgreSQL use a process per request setup, you will have a great benefit. Use cherokee or nginx (with keepalive working) you will scale smoothly.
Check that you do as much as possible of a page in a single http request (i.e. limit ajax load). Use only one cacheable css and limit the number of scripts or aggregate them in a cacheable file. Check that everything that is cacheable gets cached indeed (use firebug or chrome dev tools to find out). mic Il 17 aprile 2012 14:07, Michele Comitini <[email protected]> ha scritto: > What is your architecture? What do you use as frontend http server? > What protocol: SCGI, UWSGI, FCGI...? > Are you in a thread per request or process per request setup? > > mic > > > Il 17 aprile 2012 08:36, Bruce Wade <[email protected]> ha scritto: >> Yes you are correct plus there was 10,000+ requests a second just hitting >> the site I think I really need a load balanced. We are getting on average >> 500-1000 new members a day. >> >> On Apr 16, 2012 10:59 PM, "pbreit" <[email protected]> wrote: >>> >>> Don't forget you probably spent quite a bit if time tuning your Pyramid >>> app. >>> >>> The best ways to scale are: >>> 1) Cache >>> 2) Cache >>> 3) Cache >>> >>> Web2py makes caching queries super easy. >>> >>> If you are serving a lot of static assets, check out Cloudflare for free >>> CDN.
