Hi Jon, thanks again for helping me with this issue My concern is that there are too many instances being created all time, and only a few are created using WarmUpRequests to /_ah/warmup. My idea of AlwaysOn and WarmUpRequests was that, for a small app, most WarmUpRequets would be to /_ah/warmup and only a few would be user requests (specially when there is a traffic peek). Is that right?
The logs for today are much better, there are some /_ah/warmup requests. Today (12/14) from 7am to 10am, I had 13 loading requests (4 are /_ah/warmup requests). Isn't that too much if I have AlwaysOn with 3 reserved instances? And I understand that I always have 3 instances when checking the Instances panel; that's ok. But why there are too many instances startups and why most of them are initialized in user requests instead of /_ah/warmup requests? (And about my app traffic, I had a huge peek yesterday; but most of the time I have small traffic. Before AlwaysOn, the instances panel always reported one instance was enough) Thanks again Sergio On Tue, Dec 14, 2010 at 16:03, Jon McAlister <[email protected]> wrote: > I think the problem is that we're not doing a good enough job on our > Instances console. You do have three always-on instances, that were > initialized with a /_ah/warmup request, but we don't give you an > indication of how old they are. I do see /_ah/warmup requests in your > logs on 12/14 and 12/12. So, you had three always-on instances that > remained up for two days. You can check the Instances console at any > time to see how many always-on instances and dynamic instances are > currently running for your app. > > Your app is a bit more interesting in that it will occasionally need > more instances to handle traffic. For example, right now you have > three always-on instances and one dynamic instance. The dynamic > instance may be turned up be either a loading request or a warmup > request, in the same way that a always-on instance might be turned up > by one or the other. We try to turnup with a warming request but don't > guarantee it right now. More explanation of this is at: > > http://code.google.com/appengine/docs/java/config/appconfig.html#Warming_Requests > > 2010/12/11 Sérgio Lopes <[email protected]>: > > Hi Jon! > > Thanks for your help. I made another search for "loading_request=1" in > the > > logs and today, 12/11, I had 14 loading requests. They are all user > > requests, there is no warmup request to /_ah/warmup. Same thing > yesterday: > > 37 loading requests, not a single one to /_ah/warmup. I think it's still > not > > fixed... > > Thanks again > > Sergio > > On Fri, Dec 10, 2010 at 23:13, Jon McAlister <[email protected]> wrote: > >> > >> Hi Sergio, > >> > >> I looked into your app, and unfortunately we had a slight > >> configuration error on our part. This has now been fixed and pushed > >> out. So, it should be significantly better now. Mind having another > >> look? > >> > >> On Wed, Dec 8, 2010 at 5:49 PM, Sergio Lopes <[email protected]> wrote: > >> > Hi guys > >> > > >> > I have AlwaysOn enabled since the release, but I'm not getting the > >> > expected results. Searching my logs for "loading_request=1" I found > >> > 27 loading requests today. But only 1 of those 27 is an automated > /_ah/ > >> > warmup request, all others are user requests suffering the startup > >> > latency. > >> > > >> > My app (caelumcombr) doesn't have many requests. Before AlwaysOne, the > >> > Instances panel always reported only 1 instance for my App. And now > >> > that I pay for 3 instances (much more than needed), I'm still seeing a > >> > lot of user requests causing instance startup. Isn't that wrong? > >> > > >> > Sérgio Lopes > >> > > >> > www.caelum.com.br > >> > > >> > -- > >> > 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]<google-appengine%[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]<google-appengine%[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]<google-appengine%[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]<google-appengine%[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.
