What do you mean the site isn't in production? Or course the site is in production. And also in continuous development/deployment. Unless you call 43,340 members and $46 million through the site still in development lol
Right now my server guy has been updating the SSL on 6 back end servers that could be the reason for your deadlinks and tickets. The site has been in production for a few months now, the old version has been in production since Nov 18th. On Tue, Jul 3, 2012 at 2:45 PM, peter <[email protected]> wrote: > Bruce > > I do not quite get it. You quote all these impressive usage figures for > your site, yet it seems it is not yet in production but in development. By > just doing very ordinary things on the site and in a very brief period of > time I managed to get dead links and several tickets. Are you trying to > hype it up or something. I do recognise that you have often given valuable > feedback to the group about how to ensure that web2py sites do run > efficiently and I have learnt from your feedback. > > Peter > > > On Tuesday, 3 July 2012 19:07:50 UTC+1, Bruce Wade wrote: >> >> My site is probably the largest site using web2py at this time. >> https://secure.youadworld.com/** ignore the security warning we are >> getting the new certificates up today. >> >> This site has: >> Binary tree with over 50,000 nodes >> Ad viewer >> Custom shopping system >> MLM >> Bonus structures >> Customer support engine >> yellow pages type of site engine >> Customer rating/review/shopping engines for each business in the youad >> directory (yellow pages) >> Daily bonus calculations >> Monthly bonus calculations >> Completely customized admin section for advertisement resource >> management: ad.youadworld.com >> And a lot more. >> >> Handles over 5 - 10 million inserts into the db per day >> Has over 1 million ad views a day >> Has had over 500,000 product orders >> Is being hit with over 5000 concurrent users per second at times >> Seeing well over 20 million page views a day. >> >> The biggest issue I am facing is scaling to handle 20,000 + concurrent >> users per second. When we have 3,000 even with 3 front end servers and 3 >> database servers things slow down allot. >> >> -- -- 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
