Right now Automatic. In the case described, one.
On Nov 27, 4:34 am, Nick Johnson <nickjohn...@google.com> wrote: > What is your setting for min idle instances? > > -Nick > > > > > > > > > > On Sun, Nov 27, 2011 at 10:47 AM, sb <shaneb...@gmail.com> wrote: > > It doesn't behave this way at all. > > > It just fires up a new instance once the resident instance get > > overloaded. The resident instance goes idle. > > > The new instance then handles all the traffic, and when that gets > > overloaded another instance is created, while the original resident > > instance is just sitting their completely idle. So I am getting billed > > for three instances one of which is doing nothing and never will do > > anything until I manually intervene. > > > On Nov 26, 6:20 pm, Nick Johnson <nickjohn...@google.com> wrote: > > > On Sun, Nov 27, 2011 at 3:16 AM, WallyDD <shaneb...@gmail.com> wrote: > > > > Hi Nick, > > > > > Thanks for responding and looking into this. > > > > See my response below; > > > > > On Nov 24, 8:57 pm, Nick Johnson <nickjohn...@google.com> wrote: > > > > > On Thu, Nov 24, 2011 at 5:48 PM, WallyDD <shaneb...@gmail.com> > > wrote: > > > > > > I am having something of similar problem with instances not turning > > > > > > off. > > > > > > This isn't a problem - you're not being charged for those instances. > > > > You'll > > > > > only be charged if demand requires sending traffic to them, in which > > case > > > > > you've been saved the overhead of starting up a new instance. > > > > > I am very much being charged for these instances. > > > > > > > The resident instances do nothing and stay idle while other > > instances > > > > > > serve. Not entirely sure if it is related to your issue. > > > > > > If you've specified a 'min idle instances' greater than 0, then this > > is > > > > > behaving as documented. The point of requesting idle instances is to > > > > handle > > > > > sudden increases in traffic volume while more instances are being > > spun up > > > > > in the background; naturally this means that they have to remain idle > > > > while > > > > > waiting for a traffic spike that will require them. > > > > > The second instance fires up when traffic overloads the resident > > > > instance(s). The new dynamic instance(s) then stay on, permanently. So > > > > I get charged for both instances, one of which does nothing. > > > > You set your "min idle instances" to 1; therefore, 1 instance will be > > idle, > > > in order to handle traffic spikes. If you don't want this behaviour, set > > > min idle instances to 0. > > > > -Nick Johnson > > > > > If it is behaving as documented, which part of the documentation > > > > should I be looking at? > > > > > - sb > > > > > > -Nick Johnson > > > > > -- > > > > 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. > > > > -- > > > Nick Johnson, Developer Programs Engineer, App Engine > > > -- > > 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. > > -- > Nick Johnson, Developer Programs Engineer, App Engine -- 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.
