ok, then it is really not very helpful for performance, it is just a way to limit the cost. right?
On Sep 29, 7:14 am, Barry Hunter <[email protected]> wrote: > Sounds like you have misunderstood "Max Idle Instances". Its the > maximum number you will be charged for. It is not a guarantee. If you > have spiky traffic, it might mean you will have spare capacity ready > to handle more requests. Wont help with the first spike. > > Think you looking for "Min Idle Instances". That is only available > right now if you have purchased "Always On" I bleive. Once the new > pricing goes live, it will be open to all. > > > > > > > > On Thu, Sep 29, 2011 at 12:07 AM, Tapir <[email protected]> wrote: > > It is not very useful. > > When I set it 3, gae will still only keep one idle instances, so my > > app will still encounter slow startup when 2 visits coming at the same > > time. Setting it higher is helpless to avoid the java app slow startup > > problem. > > > I just found the only difference between set "Max Idle Instances" as 1 > > and 3 is the total used CPU hours, about 25:29, which means except the > > free 24 hours, the total used CPU hours is 1:5. > > > -- > > 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 > > athttp://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.
