If you believe this may be because of memcache API latency, please star this issue: http://code.google.com/p/googleappengine/issues/detail?id=7554
On Tue, May 22, 2012 at 11:44 PM, Daniel <[email protected]> wrote: > I'm seeing the same issue.. for the last 3 > days latency has skyrocketed and my costs have over doubled. Here's my > graph for the past 7 days > > > > <https://lh5.googleusercontent.com/-JCpRQX6MeFk/T7xrHDMMX8I/AAAAAAAAAzk/LcVjYw1awMo/s1600/skywords.jpg> > > > On Tuesday, May 22, 2012 2:04:53 PM UTC-7, Rishi Arora wrote: >> >> Here's what my milliseconds/request looks like, although the #instances >> follows a similar pattern, and translates directly into higher costs (5x >> normal usage today) >> >> On Tue, May 22, 2012 at 4:01 PM, Rishi Arora >> <[email protected]>wrote: >> >>> Perhaps similar to what I'm seeing. Although I was able to use the >>> appstats tool to determine that the deadlines were being missed >>> specifically because of memcache API calls. Perhaps you can determine from >>> appstats if its the same for you? >>> >>> If so, please star this issue that I logged: >>> >>> code.google.com/p/**googleappengine/issues/detail?**id=7554<http://code.google.com/p/googleappengine/issues/detail?id=7554> >>> >>> >>> >>> On Tue, May 22, 2012 at 2:02 PM, Robert Morgan >>> <[email protected]>wrote: >>> >>>> Beginning about 18 hours ago, the milliseconds/Request on one of our >>>> apps began to ramp and is now over 100 seconds for a trivial response >>>> (which historically takes 2 seconds). Our other apps are fine, and the AE >>>> status page is clear. >>>> >>>> It's an app that we use for development, it's been around for ages and >>>> still runs the Master-Slave datastore. Python. The ramping just started -- >>>> we had not deployed a new server version in about a week, and our client >>>> usage remains low and patterns haven't changed. >>>> >>>> I've poked at it trying to see if I can determine some threshold, but >>>> even a very simple return now fails due to DeadlineExceeded. >>>> >>>> This really feels like it's a system issue -- any ideas on what I can >>>> do next? >>>> >>>> Thanks, >>>> :R >>>> >>>> -- >>>> You received this message because you are subscribed to the Google >>>> Groups "Google App Engine" group. >>>> To view this discussion on the web visit https://groups.google.com/d/** >>>> msg/google-appengine/-/**rYY5Gw9UuE8J<https://groups.google.com/d/msg/google-appengine/-/rYY5Gw9UuE8J> >>>> . >>>> To post to this group, send email to google-appengine@googlegroups.** >>>> com <[email protected]>. >>>> To unsubscribe from this group, send email to >>>> google-appengine+unsubscribe@**googlegroups.com<google-appengine%[email protected]> >>>> . >>>> For more options, visit this group at http://groups.google.com/** >>>> group/google-appengine?hl=en<http://groups.google.com/group/google-appengine?hl=en> >>>> . >>>> >>> >>> >> -- > You received this message because you are subscribed to the Google Groups > "Google App Engine" group. > To view this discussion on the web visit > https://groups.google.com/d/msg/google-appengine/-/eDY4e0D-tH4J. > > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/google-appengine?hl=en. > -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
