I am using about 30 megs of memory cache for 1200 items -- not very much imo. In the past I have used as much as 100 megs without seeing excessive purges.
Hard to code against parameters which are not documented and possibly even change based on unknown factors. At this point, you can even assume that a memcache will be around for even a few minutes before being purged -- if it is purged that often why not just deny the memcache.set in the first place. Further, it is not even clear what you get with the premium memcache; I suspect the per gigabyte refers to the memcache bandwidth and not the amount of cache being saved. Whenever GAE changes something fundamental, they don't tell us about it and we have to try and figure out what they might have changed. Not cool imo. My guess is they penalize people not using the premium memcache which is just another way of them forcing people to move to the premium version and making the non premium version worthless. I am probably looking at a serious recoding effort to reduce my reliance on memcache. Not happy about any of this. On Tue, Oct 8, 2013 at 5:54 PM, timh <[email protected]> wrote: > 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 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.
