initially I misunderstood the maximum idle instances. it exactly means that. if your app set to 2 idle instance. your app will have as many instances as it needs. but if traffic reduces it will kill rest of the idle instance apart from last two AFTER their 15 minutes cycle over. so if there is a small spike happen which cause four instance to start for only two minutes. you will be charged for one hour since each instance will be on for next 15 minutes. so extra ( 60 - 8 = 52 minutes are charged extra ). it will not be a problem for high traffic sites which have constant and complete 24 hour smooth traffic instead of spikes. latency is simple. more latency more profit slower app. less latency less profit faster app.
am I understanding correctly now. ? On Sat, Sep 3, 2011 at 9:15 PM, Nick Rudnik <[email protected]> wrote: > I agree this scheduler needs a lot of work. I also think Google should not > be charging us based on a black box algorithm that we cannot directly > control or understand. Any defect or problem in the scheduler will > dramatically cost us when it should be Google that pays for any defects like > that. > > -- > 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/-/l8XbNUAuAbEJ. > 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.
