Memcache used to be fast, fast, fast. FWIW, we've turned off memcaching on most of our NDB models because a datastore key.get() is as fast as a typical memcache.get() and without the NDB memcaching, we don't incur the memcache (possible) miss followed by the key.get().
j On Thursday, 18 April 2013 15:28:47 UTC-6, Gerald N wrote: > > Hi, > > I have an App (online gaming) with over a million requests a day - we use > objectify4, which in turn uses memcache for caching datastore objects. > Usually, memcache is very quick - <10 ms per request. > > But occasionally (once a day a bit, once a week very significatnly), > memcache becomes very very slow, from 50-100 up to several hundred > milliseconds - which slows down my requests that get objects from objectify > and memcache down quite a bit (from around 500 ms per request with good > memcache to up to 6 seconds with "slow" memcache") and makes the game > unplayable. > > So, did anybody else also experience this issues, and is there anything > from developer side that can be done against that (i do not really want to > abadon objectify) or is this just a flaw that Google App Engine Users have > to live with like suggested in > https://groups.google.com/forum/?fromgroups=#!topic/google-appengine/3gdJKrh5DUQ > ? > > So how to archieve, constant and predictable memcache performane? > > thank you, > > Gerald > -- 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?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
