Also, I imagine going to HRD would indirectly help my situation because I'll be forced to upgrade to python2.7. So, while my instance is waiting forever for memcache to return some data, it would be available to service other requests, and keep the number of active instances low. Am I correct in this reasoning?
On Tue, May 22, 2012 at 10:59 AM, Rishi Arora <rishi.ar...@ship-rack.com>wrote: > My app usually consumes ~30 instance hours every day, and occasionally > spikes to ~35 when Master-Slave datastore latencies go up. We will be > transitioning to HRD soon, but today large latency spikes have caused my > instance hours to reach ~50 already, in the first 9 hours of the day. I > peeked at the appstats output to see where this spike is coming from, and > it appears to be memcache (see attached pic). This seems absurd and not > something app operators should be expected to pay for. Anybody else seen > this? > > Thanks in advance > - Rishi > > -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to google-appengine@googlegroups.com. To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
