for starters check the "cache" page in appadmin (go to "database administration", then click "cache" at the top) to see hot many hits/misses you find. In a "perfect world" ( i.e. your cache works as expected) you'd have 1 miss and n-1 hits with n being the number of times your page is accessed.
On Thursday, April 18, 2013 7:17:26 PM UTC+2, BlueShadow wrote: > > So you are basicly saying I did exactly what I wanted to do save the > entire generated page on disk. > So how can I find out what is taking so long for the page to load? > > @Derek: thats easy: I want the page cached from 00:05 to 23:59. because > every day at midnight the data changes. if for some reason the page is > cached later than 00:05 (I got a cronjob with a curl to visit that page) > the new version will be calculated regardless of whether there is still a > cached version or not. (because the date changes) > > On Thursday, April 18, 2013 6:41:37 PM UTC+2, Paolo valleri wrote: >> >> Basically it stores the output of the function, in your case the output >> is the rendered view. >> For more info about cache, have a look here: >> http://web2py.com/books/default/chapter/29/04#cache >> >> Paolo >> >> -- --- 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 web2py+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
