On Fri, Oct 11, 2013 at 1:02 PM, James Gilliam <[email protected]> wrote:
> 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. > Hello James, Are you experiencing this behavior across multiple application IDs, or is it one application having performance issues? What you can try is - if you have a paid support package - is to call Google up and ask them to move your app ID to a different place in the physical infrastructure. You might get better neighbors sharing your server, and less contention for memcache resources. If you don't have a paid support contract, you can try redeploying your app as Barry noted above. In addition (depending on your application's size and instance class) you may be able to cram some data into an in-instance cache. Try profiling your app and checking to see if there's some free RAM to use. With that said, I +1 Tim and Barry's comments, this just doesn't look intentional on Google's part. ----------------- -Vinny P Technology & Media Advisor Chicago, IL App Engine Code Samples: http://www.learntogoogleit.com -- 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.
