Alex, Basically, GAE had a price increase by making shared memcache unusable. You have to signup for the premium memcache at 12 cents a GB-hour to get back to the way it use to work.
This was dishonest of GAE and they have not even announced that they essentially deprecated the shared memcache since it is no longer useable for much of anything. On Wed, Oct 9, 2013 at 8:17 AM, Alex Burgel <[email protected]> wrote: > I'm experiencing the same thing as you. A few months of reliable memcache, > but now since the weekend I'm seeing the cache reset every couple of hours > and a lower hit rate. > > Nothing changed in my app (haven't deployed in a few days). > > > On Tuesday, October 8, 2013 1:24:12 PM UTC-4, 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 a topic in the > Google Groups "Google App Engine" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/google-appengine/JC4xSIJRV7I/unsubscribe > . > To unsubscribe from this group and all its topics, 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. > -- 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.
