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 On Thursday, April 18, 2013 6:17:36 PM UTC+2, BlueShadow wrote: > > Hi I got a site which calls some major calculating. So I thought lets use > the cache decoator to speed up second time loads. > But it doesnt seem to have any effekt on pageloading times. > @cache(returnDatestring()+"Somepage", time_expire=86000, cache_model=cache > .disk) > def Somepage(): > #some time intensive calculations > return response.render(l=l) > > So with and without the @cache decorator it takes about 25 seconds for the > page to load. (yeah my server is slow I know) As far as I understand it the > whole age should be stored on the disk and be served as a static page. > which should load instantly. > Or is just the output of the function stored and the view has to be > rendered afterwards? (the view has a big table with like 100 rows, there > are calculated some sums too) > If so can I cache the entire view? > -- --- 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.
