[google-appengine] Re: Downtime or memcache issue? Latency spike (up to 5/8 times) and memcache write error

Hey Cristian, This is understandable given that Memcache is shared using datacenter resources across all apps. It's likely that apps in the same location as yours also experienced the same latency for that period. You can read about Memcache in the docs

[google-appengine] Re: Downtime or memcache issue? Latency spike (up to 5/8 times) and memcache write error

Hi Nick, thank for the response. I know that the memcache response time is not covered by SLA (at least for best effort, dedicated probably have), however yesterday it was very high indeed. Because I'm using ndb and I'm using the default memcache policy my server were very slow (at a certain

[google-appengine] Re: Downtime or memcache issue? Latency spike (up to 5/8 times) and memcache write error

Hey Christian, If you don't have it installed on your app it might be too late to diagnose the past issue, but using appstats (java | python ) you could determine exactl

[google-appengine] Re: Downtime or memcache issue? Latency spike (up to 5/8 times) and memcache write error

Instead of using AppStats, you should just use Cloud Trace instead. Afaik, it does everything AppStats does, but without the overhead. On Monday, July 20, 2015 at 10:16:35 PM UTC+2, Nick (Cloud Platform Support) wrote: > > Hey Ch

[google-appengine] Re: Downtime or memcache issue? Latency spike (up to 5/8 times) and memcache write error

Great point, troberti. Very true! On Tuesday, July 21, 2015 at 12:23:46 PM UTC+3, troberti wrote: > > Instead of using AppStats, you should just use Cloud Trace > instead. > Afaik, it does everything AppStats does, but without the

[google-appengine] Re: Downtime or memcache issue? Latency spike (up to 5/8 times) and memcache write error

Thank Nick and troberti. Great suggestions indeed. And in fact I had both: app stat and cloud trace. App stats record a bit more stuff but I found cloud trace a good compromise for the rough analysis. I investigated a bit more and I found 4 major problem: 1 - memcached layer due to the usage pa

[google-appengine] Re: Downtime or memcache issue? Latency spike (up to 5/8 times) and memcache write error

Thank Nick and troberti. Great suggestions indeed. And in fact I had both: app stat and cloud trace. App stats record a bit more stuff but I found cloud trace a good compromise for the rough analysis. I investigated a bit more and I found 4 major problem: 1 - memcached layer due to the usage pa

[google-appengine] Re: Downtime or memcache issue? Latency spike (up to 5/8 times) and memcache write error

> > > PS: troberti, are you from firigames ? So I have to thank you for both > Phoenix HD and for your great BTree library! I use it a lot for my > leaderboards ;) > Heh, yes that's me :) Great to hear you use and like my BTree library! -- You received this message because you are subscribed