Hi team, previously, the scheduler used to spin up 3 instances for our application, only used 1 out of the 3, but at least we didn't have to pay for the unused instances. There was always a big gap between total instances and billed instances.
However, as of yesterday, the scheduler continues to spin up 3 instances on average, but we have to pay for all of them. We're at maybe 1 request per second on average, and it's all handled just fine by one instance. We're on F4, so having to pay for 2 mostly unused instances hurts. Since this seems to coincide with the 1.6.5 release, I'm tempted to think that there's something changed in the background, and it would be great to learn more about the new suggested way. When we tried to limit idle instances last time, all we got was instance churn and bad latency. So we're on automatic/automatic these days, and I'd prefer not to have to experiment again. Some advice would be great. That aside 1.6.5 is great of course! :) Cheers, Per -- 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.
