On Fri, Feb 21, 2014 at 1:23 AM, Tapir <[email protected]> wrote: > So for the app with warmup problems, to avoid the warmup the problem, the > real free hours would be only a little more than 4 hours, right? > And for the 15 minutes tax design, the "a little more than 4 hours" is > about several minutes in fact, right? > > Ok, I see why one hour compute hour is enough for my app but my app is > still often counted more than 28 hours now. > So you help me confirm again using Java >
The 15 minute rule is not confined only to the Java runtime, it exists for all runtimes. It's not a tax; it's there so you avoid the overhead of a second warmup request if another request comes in soon after the first. If you wanted to avoid keeping instances up for the extra 15 minutes, you could always cause the instance to terminate; for example, exceed the memory allocated to your instance. ----------------- -Vinny P Technology & Media Advisor Chicago, IL App Engine Code Samples: http://www.learntogoogleit.com -- 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 [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/google-appengine. For more options, visit https://groups.google.com/groups/opt_out.
