Last night we had a sudden traffic spike at 21:00 (CET). Requests were at a steady 40 req/s when we suddenly had more than 400 req/s. This led to our application being almost entirely down for about 10-15 minutes. I think that it’s because many new app instances are being fired up at the same time. Is there anything we can do to “prime” our application to handle these situations in a better way? Could it be that our application takes too long to start up?
Here's a graph showing number of requests/s <https://lh5.googleusercontent.com/_4q0OeYdmoDA/TVJS02W3LgI/AAAAAAAAAAU/5Xilqyh75Hs/spike_sofias_anglar.png> And here are all the errors/s <https://lh5.googleusercontent.com/_4q0OeYdmoDA/TVJTYJKeEtI/AAAAAAAAABA/MHgNGE8niWo/spike_sofias_anglar_error.png> Any ideas to how we can handle these situations? Tell people not to enter our website? ;) /Henric -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to google-appengine@googlegroups.com. To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
