a bug in memcache

0 views
Skip to first unread message

saintthor

unread,
Feb 10, 2010, 12:51:11 AM2/10/10
to Google App Engine
quote:

By default, values stored in memcache are retained as long as
possible. Values may be evicted from the cache when a new value is
added to the cache if the cache is low on memory. When values are
evicted due to memory pressure, the least recently used values are
evicted first.

when an old value in, if update an exist value, not add a new value,
cause the total value increase over 1M, the old value is still exist.
i think it should be deleted.

Ikai L (Google)

unread,
Feb 17, 2010, 1:44:37 PM2/17/10
to google-a...@googlegroups.com
What is the exact bug? I'm not sure what you're describing is how memcached is supposed to work:

Granted, our version is a bit different for security reasons, but the way memory is managed should mostly match the open source implementation.


--
You received this message because you are subscribed to the Google Groups "Google App Engine" group.
To post to this group, send email to google-a...@googlegroups.com.
To unsubscribe from this group, send email to google-appengi...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.




--
Ikai Lan
Developer Programs Engineer, Google App Engine
http://googleappengine.blogspot.com | http://twitter.com/app_engine
Reply all
Reply to author
Forward
0 new messages