We have a similar problem. I've disabled the app, so all instances were turned off and upon enabling it again, there were instantly 8 instances running. We're also seeing weird behavior as it seems that not all instances have the same state (which really puzzles me, since the app is stateless). I thought it's a problem with cache (consequent reads yielded different results), but the problem remains without cache.
We're running Play 1.1 framework. On Tue, May 3, 2011 at 3:59 PM, Eduardo Perrino <eduardo.perr...@gmail.com>wrote: > Hi!! > > We have problems with the instance feature of appengine. Today we have > got 16 instances, and we've detected that many of them when receive a > request, it has to start the application again. So our application > consumes a lot of cpu because our startup process is a little heavy. > > To solve this situation we've enabled always on feature, and the > problem becomes bigger, because always on instances has to start the > application too. > > We don't understand this behavior and we need help to solve this. > Otherwise we'll have to stop using appengine as a valid JAVA > development platform because stop and start in every moment the > application is unacceptable into this enviroment. > > > Eduardo > > -- > 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. > > -- lp, Anže -- 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.
