If you set 5 max idle instances, and the scheduler leaves 8 sitting around idle. You will not be changed for the extra 3 idle instances.
ie, its in Google's interest to honour your chosen setting, because they will be paying for the difference :) On Thu, Sep 1, 2011 at 9:48 PM, Francois MASUREL <masu...@mably.com> wrote: > Hi Greg, > Thanx for your answer. > But what does exactly mean "You will not be charged for instances over the > specified maximum." then ? > > Francois > > > > On Thu, Sep 1, 2011 at 22:43, Gregory D'alesandre <gr...@google.com> wrote: >> >> Hi Francois, thanks for bringing this issue up! Its an important one. >> Max idle instances only sets the maximum number of idle instances that >> will be running to prepare for traffic, not the number of total instances >> that can run at any one time. >> That being said "Always on" currently keeps 3 instances running for you to >> be ready to serve traffic. Under the new model you'll be able to choose the >> number of minimum idle instances you want to keep running. The scheduler >> has been tuned to take advantage of the new model but the billing comparison >> you are seeing is showing charges for the 3 always on instances that are >> running. >> The short answer is you probably want to set max idle instances to 1, once >> the new billing goes into place you will no longer see the 3 always on >> instances anymore. >> I hope that makes sense and helps! >> Greg D'Alesandre >> Senior Product Manager, Google App Engine >> On Thu, Sep 1, 2011 at 1:29 PM, Francois Masurel <f.masu...@gmail.com> >> wrote: >>> >>> I have "Always on" activated on my app (vncts1). >>> >>> I have set "Max idle instances" to 3, so I should only charged for a >>> maximum of 3 * 24 - 24 (free quota) = 48 hours : >>> >>> "You will not be charged for instances over the specified maximum." >>> >>> But I'm charged for a bit more everyday (billable column) : >>> - 08/28 -> 48.16 hours >>> - 08/27 -> 48.12 hours >>> - 08/26 -> 48.19 hours >>> Is it a bug ? >>> Francois >>> >>> -- >>> 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/-/x_43C91yPKgJ. >>> To post to this group, send email to google-appengine@googlegroups.com. >>> To unsubscribe from this group, send email to >>> google-appengine+unsubscr...@googlegroups.com. >>> 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 google-appengine@googlegroups.com. >> To unsubscribe from this group, send email to >> google-appengine+unsubscr...@googlegroups.com. >> 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 google-appengine@googlegroups.com. > To unsubscribe from this group, send email to > google-appengine+unsubscr...@googlegroups.com. > 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 google-appengine@googlegroups.com. To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
