>From my experience, an app without billing enabled will encounter many many slow cold starts. That is why although my app visits is small but I still made my app billing enabled. But today, there are suddenly many cold starts again on my app even if it is billing enabled.
On Feb 27, 12:30 am, Anders <blabl...@gmail.com> wrote: > Thanks. The app no longer has billing enabled (needed to be able to adjust > minimum instances), but that could be worth trying. > > > > > > > > On Sunday, February 26, 2012 2:26:00 PM UTC+1, Mike Lawrence wrote: > > > I noticed similar behavior. > > I think the auto setting for minimum number > > of instances changed from two to zero active > > instances. > > I changed from auto to one, and my app > > is much more responsive. setting minimum > > instances higher will co$t you more > > > On Feb 25, 9:36 am, Anders <blabl...@gmail.com> wrote: > > > In the recent weeks the cold starts for Java apps have started to take a > > > long time in my experience. More than three seconds to load a webpage is > > > too long generally for a high quality end user experience. I assume it > > > happens when the physical GAE servers become too crowded resulting in > > > sluggish cold start loading of apps from the file system (and/or maybe > > > because of delays in the distributed file system itself). -- You received this message because you are subscribed to the Google Groups "Google App Engine for Java" group. To post to this group, send email to google-appengine-java@googlegroups.com. To unsubscribe from this group, send email to google-appengine-java+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en.
