On Sunday, August 4, 2013 11:26:25 AM UTC-4, Loïc wrote: > Hello Massimo > > Could you please elaborate the following sentence, and if possible give an > example of what we should do/avoid? > > "built-in system is ok if you have one web2py instance and if you reuse > the same keys else you can have a memory leak (keys do not expire with > cache.ram)." > >From the book:
Note, time_expire is used to compare the current time with the time the requested object was last saved in the cache. It does not affect future requests. This enables time_expire to be set dynamically when an object is requested rather than being fixed when the object is saved. This means that once saved to the cache, objects are never removed from it automatically (i.e., they don't get removed after the time_expire period has elapsed). So, if you keep saving lots of objects to the cache with unique keys but never explicitly remove those items, the cache will continue to grow and grow. Anthony -- --- 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.
