Warm up requests has the biggest impact on apps that have slow warmups. I have my warm up at less than 100ms (average much lower than that) so there is no advantage really for me.
If your warm up time is something like 3 seconds, that is 3 seconds that your user doesn't have to wait if their request would cause a new instance. The cost is a function of the Dynamism of your application. If you cruise along at 4 instances Burst to 40 for 15 minutes twice a day, then warmups will be a larger cost than if you cruise along at 40 all day and burst to 15 once in a while. Warm ups will fire on apps with steady traffic to replace over loaded instances that were killed for hitting their soft memory limit. On my app instances recycle every 1,600 requests, so if I run warmups I typically add 1/1600th of my total price to warm ups (that's pretty small) and 1/1600th of my requests don't get hit with up to an extra 100ms for the spinup. -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Vivek Puri Sent: Friday, December 09, 2011 10:41 AM To: Google App Engine Subject: [google-appengine] Warmup Requests For an application with 40-50 idle instances, is having "warmup requests" feature useful? If answer is yes, and we need to switch on the option, what be the impact on the cost? -- 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. -- 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.
