Normally, these requests take under a second to satisfy, two seconds at most. However at 2012-10-17 09:47:44.811 4 new instances were spun up for 4 requests in a row. It is my understanding that Chrome is limited to a certain number of concurrent requests per host. How could a single browser session overwhelm Google app-engine? The result on the back end was 5 instances where only one was needed. The result on the front end was 30 seconds of waiting around. After a few minutes, the scheduler begins killing off the new instances. Then the problem repeats itself.
There were no warmup requests issued. My app is set up to handle them. This is behavior can be reproduced. The appid is lemurspot. Please make sure that the next time the engineers mess with the dark powers of the scheduler, they draw their pentagrams correctly. And don't use frozen goats blood. ;) -- 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/-/svt12OuuPg0J. 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.
