I just asked: We still have a maximum budget. No need to worry about that. On Sep 2, 8:23 pm, Stephen Johnson <[email protected]> wrote: > There still needs to be a maximum. A daily rate can still be exhausted by a > denial of service. Worse yet when AppEngine has issues such as datastore > issues, memcache issues, task queue issues and all the other issues it has, > it can cause your latency to rapidly increase even though your requests are > failing. The scheduler will then start spinning up instances to serve bad > requests and eat your daily quota for now good reason. In my opinion there > needs to be a Max. Active Instances and also we should be able to set > Minimum Idle Instances to zero. Not sure why it can only be set to 1. > > > > > > > > On Fri, Sep 2, 2011 at 11:07 AM, Philip <[email protected]> wrote: > > I would think that we can still specify an upper limit for instance > > hours but some clarification would be nice. > > > On Sep 2, 7:59 pm, Stephen Johnson <[email protected]> wrote: > > > I mean a Maximum Active Setting (not the idle setting which is useless > > > against a denial of service attack). > > > > On Fri, Sep 2, 2011 at 10:59 AM, Stephen Johnson <[email protected] > > >wrote: > > > > > That's only for idle instances but if they are actively serving request > > due > > > > to a denial of service which is Brandon is talking about then you will > > be > > > > charged. There definitely needs to be a maximum setting. > > > > > On Fri, Sep 2, 2011 at 10:54 AM, prgmratlarge <[email protected] > > >wrote: > > > > >> Quoting from > > > >>http://code.google.com/appengine/kb/postpreviewpricing.html#scheduler. > > .. > > > > >> Max Idle Instances: Decreasing this value will likely decrease your > > > >> bill as fewer idle instances will typically be running and we will not > > > >> charge for any excessive idle instances. In this case the scheduler > > > >> knob is a suggestion to the scheduler but we will not charge you for > > > >> excess if the scheduler ignores the suggestion. For instance, if you > > > >> set Max Idle Instances to 5 and the scheduler leaves 16 instances up > > > >> for some length of time, you will only be charged for 5 instances. > > > > >> In other words, even though there may be more than your max, you will > > > >> only be charged for your max. > > > > >> On Sep 2, 1:02 pm, Seb <[email protected]> wrote: > > > >> > Hi, > > > > >> > I've set "Max Idle Instances: ( 1 ) " > > > >> > and "Min Pending Latency: ( 15.0s ) " > > > >> > but, after waiting 15 minutes, there are still 2 instances > > presents... > > > > >> > The latency of the requests are less than 1 seconds... > > > > >> > How can I get only 1 instance??? > > > > >> > Thanks, > > > >> > Seb. > > > > >> -- > > > >> 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.
-- 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.
