Err, I guess there are varying levels of "sure" as well. It overwrites least used data rather than oldest data.
http://code.google.com/p/memcached/wiki/FAQ#Item_Expiration Richard On Apr 20, 2011, at 10:34 AM, Richard Revels wrote: > I am sure it will overwrite old data if it becomes full. The other thing I > was mis-remembering. Here is an excerpt from the wiki. > > There isn't a "rule of thumb" when picking an expiration time. Sit back and > think about your users, and what your data is. How long can you go without > making your users angry? Be honest with yourself, as "THEY ALWAYS NEED FRESH > DATA" isn't necessarily true. > > Expiration times can be set from 0, meaning "never expire", to 30 days. Any > time higher than 30 days is interpreted as a unix timestamp date. If you want > to expire an object on january 1st of next year, this is how you do that. > > > And the wiki link. > > http://code.google.com/p/memcached/wiki/NewProgramming#Expiration > > Richard > > On Apr 20, 2011, at 10:14 AM, Brett Nemeroff wrote: > >> On Wed, Apr 20, 2011 at 9:09 AM, Richard Revels <rrev...@bandwidth.com> >> wrote: >> Forever is a long time. If memcached fills up it will start booting out old >> entries to allow new ones to be stored. I seem to remember there being a >> month time limit on entries as well but that might be only if you are >> setting a timeout value. Too bad I can't used memcache to replace my feeble >> memory... >> >> >> Richard, >> Are you sure about that? I don't remember memcache having that problem. I >> certainly don't remember any kind of "default" time limit. >> _______________________________________________ >> Users mailing list >> Users@lists.opensips.org >> http://lists.opensips.org/cgi-bin/mailman/listinfo/users >
_______________________________________________ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
