Thanks this is very helpful to know. I am building a system with nginx and uwsgi to get the system running on that. I have been avoiding using uwsgi for anything serious because I have been seeing a lot of threads reporting problems with it.
Michele thanks for the feed back I am working on implementing your 10 steps and will use the profiler to see where things need to be optimized. -- Regards, Bruce On Tue, Apr 17, 2012 at 1:47 PM, Michele Comitini < [email protected]> wrote: > As always Massimo is also correct on this. > Do not try to optimize code before the profiler says where to optimize. > Use the profiler any time you want increase performance of the code > you wrote, it helps you save much time, since unless you optimize > every line of code you will end optimizing things that do not impact > on the overall speed. > > mic > > Il 17 aprile 2012 21:29, Richard Vézina <[email protected]> > ha scritto: > > Massimo post : > https://groups.google.com/forum/#!topic/web2py/hB3y_6gFIi4 > > > > Pretty instructive on speed trouble shooting. > > > > Richard > > > > > > On Tue, Apr 17, 2012 at 3:02 PM, Ron McOuat <[email protected]> > wrote: > >> > >> I ran across newrelic.com which offers profiling for Python web apps > >> amongst several other environments. I did a search on the web2py users > list > >> and found a few threads about a problem using LIKE % values with > PostgreSQL > >> but it appears to have been resolved. It looks like it might help with > >> identifying the problems areas which helps find the low hanging fruit > for > >> caching. Does anyone else have experience with using this tool? You can > use > >> it for a 2 week trial, then there is a cost. I am not associated with > them > >> and have not used the product in any way, just passing on the fact they > >> exist. > >> > >> Ron > >> > >> > >> On Tuesday, 17 April 2012 10:10:08 UTC-7, Bruce Wade wrote: > >>> > >>> Currently I just had 1 server running apache mod_wsgi using the same > >>> configuration as pyramid. However I just got approved for a few grand a > >>> month to spend on server resources, so I am looking at load balancers. > And I > >>> will put nginx in front of apache, and also start using a lot more > caching. > >>> > >>> On Tue, Apr 17, 2012 at 5:15 AM, Michele Comitini > >>> <[email protected]> wrote: > >>>> > >>>> One more thing make css and js packed + server side gzipped (nginx and > >>>> cherokee can do also gzip caching) > >>>> > >>>> mic > >>>> > >>>> Il 17 aprile 2012 14:12, Michele Comitini <[email protected] > > > >>>> ha scritto: > >>>> > 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. > >>> > >>> > >>> > >>> > >>> -- > >>> -- > >>> 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 > >>> > > > -- -- 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
