Hello Bruce, The bottle neck is always the database. 1M reqs/day is 7 reqs/minute. It is not too much but make sure:
static files are not served by web2py you cache as much as possible If you need a code review to spot possible problems, let me know. Massimo On Saturday, 7 April 2012 08:59:20 UTC-5, Detectedstealth wrote: > > Hi, > > So now that my site has been developed with web2py I am now looking to > release it this month. However also this month we were hit by a sudden > increase of members 10,650 new in the last 2 weeks which doesn't look to be > slowing down. We are getting around 100,000 - 800,000 ad views a day. > > Is this approach still the best option for scaling? > http://www.web2pyslices.com/slice/show/1360/high-availability-cluster-with-poundWe > currently have 6 servers so this may work well. But is there some more > detailed information on this approach where it has been proven to handle > the load? > > -- > -- > Regards, > Bruce Wade > http://ca.linkedin.com/in/brucelwade > http://www.wadecybertech.com > http://www.fittraineronline.com - Fitness Personal Trainers Online > http://www.warplydesigned.com > >
