If you had network issues between locations, your traffic could be less evenly distributed, and would as a result make your app "peakier".
Set your max pending latency higher and your cost won't fluctuate when network latency changes the instantaneous request rate. From: [email protected] [mailto:[email protected]] On Behalf Of Nathan Skone Sent: Thursday, May 17, 2012 2:52 PM To: [email protected] Subject: [google-appengine] Unexplained traffic loss We have over 300 machines distributed across the US calling an API once a minute, which means we should always have a base level of traffic of at least 5 or 6 requests per second. However, today we are seeing pits in our requests per second graph that show the traffic dropping to zero, then spiking directly afterward. We have not deployed any new code recently, or otherwise touched our application in any way. This traffic pattern has doubled our costs compared to a normal day. A screenshot is attached. Thanks, Nathan Skone -- 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/-/NBgU5Omj9hQJ. 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.
