That's how I *thought* it would work too, by when trying to change "Max Idle Instances" to 1 or 2, the setting does not stick - it is flipped back to "automatic" after clicking the save button. So "always on" would cost at least $1411yr. I probably have to switch to a more responsive platform.
On Sep 6, 7:37 pm, Barry Hunter <[email protected]> wrote: > One thing to realise about the before and after 'prediction', it just > shows what the cost would be at the current settings. > > With a few simple tweaks to the settings for the application, you can > probably reduce the price substantially. > > http://code.google.com/appengine/articles/managing-resources.html > > (eg, 'always on' means you have 3 instances always running. With the > settings you can bring it down so that there are only instances being > spun up to serve requests. Can make it so there is still an instance > ready to serve request - ie one instance 'always on' - which would be > your free instance. Then when you have spikes of traffic, you would > pay for extra instances. These might well fit in the $9 month minimum > spend anyway. ) -- 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.
