Did not see this in a thread search. Pretty sure I would be safe making this assumption, but thought best to check.
Question (background if you're interested is below): If a few thousand items are added to memcache each with a 30 second life, will this volume of time-based auto-evict items cause any performance / instance-increasing issues?? I'm assuming no, however: "Whenever you assume, you..." Thanks, stevep Background: I want to avoid consistency errors when selecting tasks from a query list. When a task is assigned it is "checked out" by incrementing a checkOut count on my Task class (checkOut count is a query filter item). Unfortunately the Task class has one somewhat large composite index to support the query, so my put() updates will be a bit resource intensive. I had thought that each time a checkOut count put() update is done, I would add an memcache value with the key_name of the entity being put() and specify something like a 30 second duration. When the query result of available tasks is iterated, a memcache call that successfully gets the key_name for the current iteration would indicate a consistency issue, and that entity would be skipped. Does not have to be perfect -- can live with some double assignments, but would like to catch most. Not a high-volume app, so worst case might be a few thousand such active memcache values living some part of their short lives. -- 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-appengine@googlegroups.com. To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
