I would check the totals of how much you are storing in memcache. There seems to be a high water mark (never seen it documented) which once you exceed there is a lot of churn. I have noted in the past that memcache can be affected locally. (ie one instances contents of memcache gets purged a lot, whilst another see's long retention times, which means there has to be localized effect in the infrastructure.)
On Monday, October 7, 2013 2:57:02 AM UTC+8, 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.
