In order for them to be idle, they must start. They can either start as a result of a user facing request or a warmup request. If you don't want your users to suffer the latency or your instance startups, then warmup requests are still relavant.
I do understand the new scheduler settings. Let me know if I can answer any of your questions. ;) -Mike On Sep 5, 8:29 pm, Tapir <[email protected]> wrote: > Do you understand the new app settings?! > If you have 3 idle instances, warmup is just waste your money. > > On Sep 5, 11:04 pm, Mike Wesner <[email protected]> wrote: > > > > > > > > > It is not useless. It does the exact same thing it did before, gets > > your instances hot so that they can serve user facing traffic as > > quickly as possible (without the startup overhead). Making your code > > perform well and it's cost are no longer aligned under the new > > pricing. > > > On Sep 5, 3:04 am, Tapir <[email protected]> wrote: > > > > I think it is totally useless now. > > > It conflicts with "number s of idles instances" setting. > > > > Tim Hoffman wrote: > > > > I would think your mad to use a framework with a typical startup time > > > > for an > > > > app instance > > > > of 10 secs if your only going to serve 100 requests a day. > > > > > As I said the value of /_ah/warmup depends on the situation. > > > > > Tim -- 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.
