Until yesterday my app: rundouble-hrd, ran comfortably within a single instance, and did so right though our busy summer period. It typically never breaks the 28 instance hours, unless I trigger a backup.
Yesterday it clocked up 20c or so in instance hours. Now, whenever I look at the "Instances" page, there are always 3 running. If I kill any they respawn almost immediately. I didn't change anything, what is happening here? My Java application is running in multi-thread mode, so it should serve a LOT more requests before it starts bumping up the instances. Also, I've notices that the latency on some requests is ridiculously high - again I've not changed anything here. It seems like a change has been made to the way instances are spawned, and this is effecting my costs. Right now this doesn't pose an issue, however, it does mean that I won't be able to scale my app on AppEngine, and as my demand increases I will be forced to move to another platform - I really don't want to do this, because I've long been a big fan of App Engine. -- 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/-/wlKCZJbu104J. 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.
