Always on and request every minute will not do the same thing. You are attempting to be the scheduler and that is less efficient than having them do it. And No if you always on, then your instance will start before it is needed in anticipation.
Don't try to over engineer a solution. Your Warm up Chron may not go to starting a second instance, and if you are running python if that request and a real request comes in you might be tying up the real instance you were trying to access. From: [email protected] [mailto:[email protected]] On Behalf Of Sarang Sent: Monday, May 23, 2011 9:06 PM To: [email protected] Subject: Re: [google-appengine] Poor performance since the past 2-3 days Brandon: I can understand a few seconds delay for the load request to complete. But not 100-500 seconds. And this was not the case earlier. This behavior started 2-3 days back. Warm up requests are being sent every second via the python method as described in the doc, so load request should not take this much time in any case. Even if I buy always on, when the 4th instance is needed, will it be the same case? Nickolas: I am not doing anything. The landing page is a static page. I even created a dummy page with almost nothing and I am still seeing the same behavior. Is there anyone from Google (official) able to reply here? How do I reach them? What is the best way to get such issues resolved? Thanks Sarang -- 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. -- 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.
