Why can't I get only 1 instance enabled?

[Seb]

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.

[Bay]

You cant. Either by design or because of a bug. We won't know until someone from the GAE team replies. They have not.

[Barry Hunter]

I imagine the scheduler has a longer memory. It knows its recent
behaviour for your app, and doesnt make sweeping changes. Ie it takes
time for it average 'out'

Wait longer for a start.

remember you are not been changed by instances yet. Charges dont take
affect for over 3 weeks. What's the hurry? :)

(and even then you have $50 to spend until issues with the scheduler
are ironed out)

> --
> You received this message because you are subscribed to the Google Groups "Google App Engine" group.
> To post to this group, send email to google-a...@googlegroups.com.
> To unsubscribe from this group, send email to google-appengi...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
>
>

[Bay]

The hurry is that if its not a bug - but by design - people should be warned not to begin exessive efforts learning and writing GAE-apps AND those using it currently should begin rewriting for AWS and similar services asap to avoid either extreme costs or downtime.

[Seb]

Thanks for all your answers.

Bay is right. The hurry is that it takes time to modify code if needed
or to switch to another system. I have a 400% price increase for 1 app
and that is way tooo much for me... So, I (and my clients) need to
know what to do now... $50 is nothing compare to the 400% up...

[Brandon Wirtz]

You can’t set max total instances.  GAE dynamically scales.  We recently experienced an attempted DDoS on one of our sites and that ran up a $60 bill in 24 hours (two calendar days) instead of the $3 the site usually has.  We would have eaten this any way, but in playing, I could easily create a script that would run on dreamhost that would cost a GAE user $1,000 a day, with no means for a GAE user to block it.

 

I have also had the Google Bot, and the Google DOTS Bot hit my site for $20 worth of hosting in a day.

--

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/-/2z0vMkdmdP4J.

[Joseph Lebel]

Quoting from http://code.google.com/appengine/kb/postpreviewpricing.html#scheduler_knobs_affect_billing

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.

[Stephen Johnson]

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.

--
You received this message because you are subscribed to the Google Groups "Google App Engine" group.

[Stephen Johnson]

I mean a Maximum Active Setting (not the idle setting which is useless against a denial of service attack).

[Philip]

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 <onepagewo...@gmail.com> 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 <onepagewo...@gmail.com>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 <yossiele...@gmail.com>wrote:
>
> >> Quoting from
> >>http://code.google.com/appengine/kb/postpreviewpricing.html#scheduler...

[Stephen Johnson]

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.

[Philip]

I just asked: We still have a maximum budget. No need to worry about
that.

[Stephen Johnson]

Good to know you're ok with a datastore latency spike at 2am that causes a lot of new instances to be spun up eating up your daily quota and you being down the rest of the day.

[Francois Masurel]

Good point Stephen.

[awx]

What's so asinine is that the new pricing is penalizing exactly the
opposite of what GAE used to champion. The more elastic you make your
app, the more you are charged.

Now I feel like I'm locked into a crappy, high-priced VPS ecosystem -
one that's limited, slow and unreliable. It's hard to believe that
with the design of GAE and all the limitations of GAE that Google
can't run any cheaper than this.