I try and/or evaluate all the suggestions. The worse day for shared memcache was Saturday. Today and yesterday was much improved. However, they still more aggressively purge shared memcache than they use to. I know this because I track it everyday. The premium memcache is great function since it allows more cache; however 1 gig is too much for me and too costly ... $1100 a year. Not reporting the real time billing correctly is a pain but something I can live with. No idea if they depreciated the shared memcache on purpose to force me into premium, but whatever they did screwed me -- that is for sure.
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 google-appengine+unsubscr...@googlegroups.com. To post to this group, send email to google-appengine@googlegroups.com. Visit this group at http://groups.google.com/group/google-appengine. For more options, visit https://groups.google.com/groups/opt_out.
