Hello, I'm using the pylons global cache object to cache a variety of data. I've noticed that beaker never clears expired values. It will refresh expired values with the passed create function when the are accessed, but expired values are never removed. This makes it hard to use beaker as a general cache as things that aren't touched for some time just build up in memory. I've run into this a number of times, but I'll give one solid example.
My application uses facebook to get information on a user. We are allowed to cache this information for up to 24 hours, and for performance and stability reasons, its definitely in our interest to do so. However, using beaker just leads to unbounded memory usage. If a user hasn't logged in in a few days, there's no reason for us to still have his expired data lying around. Of course, this is fairly easy to fix. We can just run a cleanup thread every few minutes to clear out expired values. However, this seems like a bit of an oversight in a piece of software designed for long running processes. Is there anything in beaker that I've missed that addresses this? Should there be? Also, does this apply to sessions? Are old sessions kept around indefinitely? I haven't looked too much at them, but I have to imagine the situation is similar. Thanks, Justin --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To post to this group, send email to pylons-discuss@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/pylons-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
