Can't say I have noticed any significant difference in memcache other than the usual week or so of instability when they roll out new releases.
Hit count:70713Miss count:5933Hit ratio:92%Item count:1979 item(s)Total cache size:40909470 byte(s)Oldest item age:23 hour(s) 36 min(s) 40 second(s) T 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 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.
