Just saw this in the Pre-release documentation for 1.8.6 - this seems like it will be helpful to you moving forward. Work for this change (upgrading the memcache backends, etc) may also have contributed to the amount of flushing you've seen:
- A memcache size chart has been added to admin console's dashboard. Access it via the drop-down above the graph. The chart graphs memcache size over time enabling customers to determine when cache flush events occurred. This is a preview feature. Unfortunately, memcache is inherently unreliable (by design) in GAE - they shut it off all the time when data center maintenance is going on. The above graph will at least help with visibility on how memcache performs. I do think it would be helpful for small shops to have a lower priced dedicated/guaranteed tier for memcache. The 100/month is going to be more than small shops who pay for a one, two, or even three reserved instances pay for the actual instances. Right now I suspect that Google is considering the shared service good enough for these smaller hosted apps, but I can imagine having a more "stable" 50-250MB memcache instance would be hugely useful for a lot of apps. On Tuesday, October 8, 2013 12:24:12 PM UTC-5, James Gilliam wrote: > > Memcache continues to perform poorly; I suspect they are making many > changes to it. > > Saturday was awful -- aggressively purging memcache, Sunday was better, > Monday was worse than Sunday. > > At this point, not sure what to do ... are we dealing with just code > instability or some fundamental change? > > Really wish GAE would test these changes before deploying them. > > Or at least alert the community to whatever changes they are making. > > On Sunday, October 6, 2013 11:57:02 AM UTC-7, James Gilliam wrote: >> >> GAE has drastically changed the way MEMCACHE works; as a result my >> application (ogeekcom) overall usage jumped by approximately 5 times with >> the same approximate bandwidth output. Like a 400% increase in price. >> >> Specifically, they are purging shared memcache very aggressively -- >> possible in an effort to force people to signup for paid memcache. >> >> As a result of this change, my application is using many more datastore >> reads and many more instances to compensate for the poor memcache >> performance. >> >> Like always, this was done without any announcement at all. >> >> If they made this change to increase make applications cost more to run, >> it is illegal. >> >> There is no problem with them offering a premium service for memcache, >> but it is illegal to degrade the previous service to force people into the >> paid model. >> >> -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/google-appengine. For more options, visit https://groups.google.com/groups/opt_out.
