Hi Greg, I haven't looked into the details of the incoming requests, I will do that when I have a bit of time, but it probably doesn't matter too much to me anymore. I've pretty much decided I will have to pay $9/month for an estimated average 10-15c per day of usage, since 1k XMPP Stanzas/day is definitely not enough for my app... Don't suppose that $9/month minimum could be reconsidered?
I guess I understand what the scheduler is trying to do, and I don't see the problem anymore now that I've setup a 1 min heartbeat to keep the instance up. It does spin up extra instances occasionally when the XMPP or Datastore API chokes up and causes an ApiDeadlineExceededException. I guess it shouldn't matter after I enable billing and will be able to set min idle instance to 1. Probably a minor issue though, but with Min Pending Latency set to 15s and my instance loading time being ~5-6s, should the scheduler be opening a new instance? I think it could be smarter because it shouldn't be necessary to open a new instance when it knows that another one is in the process of being opened. Not that it really matters now that I understand we will be charged for Max Idle Instance + Active Instances -- 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/-/WUf5N1iLntkJ. 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.
