Quote: In addition, there is a 15-minute charge ($0.02) every time an instance starts....
Sorry to keep banging on about this, but see the latest explanations of how the pricing works... what you report here is what we all heard, but it's not true. A maximum number of "max-idle-instances" have a 15-minute charge every time they start up (in return for which they'll stay in memory for at least 15 minutes) but any instances beyond that count do NOT have a 15-minute charge for starting up, they are charged only for the time they are actively serving requests (subject, I expect, to some granularity in the billing system, but this should be considerably less than 15 minutes). If you have max-idle set to 1, and a 1 minute massive burst meant that 100 instances were started, but then the traffic died back to nothing, then only 1 of those instances would have the 15 minute charge (and would be effectively guaranteed to stay in memory that long) - the scheduler may even decide, if the machines are not needed for other apps and there's spare capacity, to keep some or many of the 100 instances in memory (there may be another burst), but even if it does so, you're not paying for the other 99 being idle - it's what I termed the "free-idle" state. Cheers -- Tim -- 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/-/wFY7XNN8yzsJ. 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.
