Your waterfall showed only static files, which are served before web2py hits any of your application code, so most of those optimizations shouldn't have an impact. Are the high TTFB values only for the static files? Is web2py even serving the static files, or is the web server (e.g., Apache) doing it directly?
Anthony On Wednesday, April 10, 2013 11:41:00 AM UTC-4, BlueShadow wrote: > > migrations are false and lazy tables are true. > I tried to do something with cache.ram (for another app) which had no > effekt at all perfhaps I did it wrong. > consider moving code to (imported) modules #I started on it when I > realised I was using request.folder in my sitemap funktion which I > currently have in a module (which isn't that smart I know thats one of the > first things I will change) > > I don't know how to deal with those two points: > 5. Add session.forget for methods which don't use the session object. > #when I dont use session.something I can add the session.forget to the > beginning of the controler? > 6. Enable connection pooling depending on the database. #no idea what to > do here > > > haven't tried any of those: > compile the app #haven't tried > controller-specific models #I only use two controlers > database indexes #don't know what it is > > > > On Wednesday, April 10, 2013 5:30:10 PM UTC+2, BlueShadow wrote: >> >> Thanks Ricardo for that idea with curl. I did that 5 times the ttfb is >> almost the total time. the total time having 0 to 1 ms more than the ttfb. >> the average time is 201 ms which seems to me pretty big considering its a >> localhost request. >> when I did that test application(welcome app) I got an average about 80 >> ms which seems pretty slow too (localhost no db requests...). >> when I do the test with webpagetest I get around 300 ms for the TTFB, for >> each file the green bar(ttfb for that file is ~160 ms >> > -- --- You received this message because you are subscribed to the Google Groups "web2py-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
