Hi Tim, In your case, I think what would suit you well is to set max-idle-instances=1 (you've already done that) and min-idle-instances=1. The latter knob is not yet available but will be available once the pricing rollout is complete. In the short-term you could have a cron job keep your instance alive by sending it requests once per minute.
On Wed, Aug 31, 2011 at 5:44 PM, Tim Hoffman <zutes...@gmail.com> wrote: > Hi > I turned off always on, and set max idle instances to 1, to see what sort of > impact it would have on my predicted billing. > New billing suggests just having the equivalent of always on will cost > around $90 per month. > However with max idle instances set to 1, I frequently see no instances. > There are no errors in the log, > the scheduler is just shutting them down. > I can deal with just one idle instance, or maybe none if I can keep memcache > primed, > I can start a new instance and server from memcache < 200ms (M/S) > But I would like to see what it runs like with 1 permanent idle instance. > Thanks > 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/-/Gm8BmxcgiL8J. > To post to this group, send email to google-appengine@googlegroups.com. > To unsubscribe from this group, send email to > google-appengine+unsubscr...@googlegroups.com. > 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 google-appengine@googlegroups.com. To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
