Hi We are seeing unexpected memcache behaviour during high load and have confirmed it in a small test app.
In the following thread http://groups.google.com/group/google-appengine/browse_thread/thread/45272062a8e36545/2289806f3f711c09?lnk=gst&q=memcache+atomic#2289806f3f711c09 Ryan Barrett says that: "as for the datastore, and all other current stored data APIs like memcache, there is a single, global view of data. we go to great lengths to ensure that these APIs are strongly consistent." I interpret this as: "If our application successfully sets a memcache value for a particular key, then no matter how soon after and no matter on which application instance we try to access that key again, then it will return the value just set" If that interpretation is correct then we think that there is a problem somewhere, because we are seeing very inconsistent behaviour on memcache (i.e. different values coming back for different requests for the same memcache key) when we stress test our application with a lot of concurrent requests. If anybody could shed some light on this for us it would be much appreciated. Best regards, Morten Nielsen --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en -~----------~----~----~----~------~----~------~--~---
