The problem looks to have been resolved at 21:00 GMT. I spoke with a member of the trace team, and my issue was answered with requests for my source.
Jeff's observation about cloud debugger is very interesting, though I didn't see that in my traces. I just saw a 6 second delay before my first RPC. I was suffering 500 (error 121) on about 5% of my requests. Keith On Monday, 1 February 2016 16:48:09 UTC, Keith Marsh wrote: > > Moving this to the issue tracker. > > On Monday, 1 February 2016 14:25:24 UTC, Keith Marsh wrote: >> >> Hi >> >> On a project's default module that normally returns sub 100mS latency, >> I'm seeing latency of > 6,000mS since 10am this morning when cloud >> monitoring reported problems (and has been on and off since). >> I've switched from using shared memcache to private to see if that was >> the issue. >> Tracing isn't reporting RPC as the issue. Task queues are fine, and >> other modules are fine. >> The project hasn't been updated since Nov 15. >> I have other projects that aren't seeing any latency issues, and wondered >> if I'm in an A/B test of some sort. >> >> Anyone else suffering latency issues ? >> >> Thanks >> >> Keith >> > -- 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 https://groups.google.com/group/google-appengine. To view this discussion on the web visit https://groups.google.com/d/msgid/google-appengine/44799ef1-6427-4264-a427-415b2545c67c%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
