On Wed, Feb 19, 2014 at 5:05 AM, Tapir <tapir....@gmail.com> wrote: > > > On Wednesday, September 14, 2011 6:04:15 AM UTC+8, Rishi Arora wrote: >> >> It really doesn't matter it a second instance kicks in to process your >> user-facing requests. If your max_idle_instances is set to 1, then you're >> only paying for one idle instance at any given time. > > > Really?! Any googler can confirm this? I set max-idle-instances as 1, but > I am still charged more than 28 hours often recently. >
Can still have one idle instance. So one active instance, and one idle, means would use up the quota. Or a spike where say three instances are started, and immidiately become idle. They sill still be 'charged' for 15 minutes. If at the end of the 15 minutes, they are not shutdown you will still be 'charged' for 1 idle instance. But max_idle_instances means those two other ones become free. If you want to avoid appengine keeping (and charging you for!) idle instances, best to set max_idle_instances, back to 'automatic' https://developers.google.com/appengine/docs/adminconsole/performancesettings#minimum -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-appengine+unsubscr...@googlegroups.com. To post to this group, send email to google-appengine@googlegroups.com. Visit this group at http://groups.google.com/group/google-appengine. For more options, visit https://groups.google.com/groups/opt_out.
