Thanks Nathan. I understand. What if the value does exist (not pushed out or not expired yet)? Is it still possible to end up with a cache miss?
Peter Chiu Chief Architect Jobs DB Hong Kong Limited Direct : (852) 2170 3162 Fax : (852) 2332 2225 Email : [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> Address : 32/F, Prosperity Millennia Plaza, 663 King's Road, North Point, Hong Kong <http://www.jobsdb.com/HK/EN/V6HTML/Home/About_JobsDB/Nielsen_survey_2.h tm> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Nathan Schmidt Sent: Friday, November 02, 2007 10:09 AM To: Peter Chiu Cc: [email protected] Subject: Re: cache miss even if the value exists? It's certainly possible if you've subsequently written other keys to the server and they push the original key out to make room for that newer content. You'll usually keep your most frequently used keys since memcached moves items down the priority list for flushing as they're fetched - if you're not using expire flags it ends up being basically a least-recently-used cache. -n
<<image001.gif>>
