I would like to be able to limit *active* instances too. Particularly for my 'testing' applications. I don't want to have 20 or 30 instances spun up while I'm testing stuff. Would prefer to limit it.
It would be handy to prevent hitting over-quota errors at the risk of degraded performance. Robert On Sat, Sep 10, 2011 at 11:39, Gerald Tan <[email protected]> wrote: > I wished Google made it clearer, but guys, please stop worrying about the > Blue "Total Instances" line when it comes to billing. You are NOT charged > for the Blue line, but for the YELLOW "Active Instances" line plus 1. Your > actual Instance-Hour change is "Max Idle Instance plus Active Instance" > (except when you have 0 instances up where you will be charged 0). > > If you set Max Idle Instance to 1. Your free application should have no > problem staying under the 28 Instance-Hour quota even if the scheduler > decides to spawn 2-4 instances for you all day, as long as your "Active > Instances" average is below 0.1666 > > Again, IGNORE THE BLUE LINE. Worry about keeping the YELLOW line below > 0.1666 > > -- > 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/-/FGV2F-eHOXMJ. > 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.
