On Mon, Jul 30, 2012 at 11:15 AM, Marcel Manz wrote: > > Certainly I could measure those latencies myself and store the information > in memcache for subsequent requests,
I would think you would have to. AppEngine is massively distributed, operating out of multiple data-centres. So the latencies you see accessing APIs are only really going to apply to your little corner. The (taskqueue) server you happen could be seeing very different access patterns to another one. In fact different instances of your app, might even be experiencing different latencies, because they may be seperated into different parts. Although it makes sense for AppEngine to keep your instances clustered so can for example use a local memcache server. So rather than memcache, use instance storage to store API health data? -- Its one of the reasons you see so many people complaining about the AppEngine Status site - it can be showing 'all fine' when someones particular app is massivly degraded. AppStatus would have to make sure it has instances running in every corner of AppEngine datacenters, and possible report 'best/worse/average' or something. -- 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.
