I am having this problem for the last week or two after months of good performance and very little recycling. As my app start up time is around 15 seconds this is really hitting my user experience in a negative way.
On Jan 16, 12:32 am, Ikai Lan <[email protected]> wrote: > Hey everybody, > > We've been seeing more and more reports of applications being cycled out > overly aggressively, resulting in some folks implementing (discouraged) > workarounds to keep their application from being cycled out. > > - What is your application ID? salsa-amsterdam > - How do you know it is being cycled out? You'll need to insert some code > that only gets called when the app cold starts. I have some logging which is executed on startup > - How much time of inactivity does it take before your application is cycled > out? Can be as little as a minute. > - What time or days does this seem to happen? Seems to happen all the time. > - What frameworks or libraries are you loading? Just the plain Servlet API and Groovy. > Any other information you can provide would be helpful. Start up time of the app is about 10 seconds and involves some on the fly compilation of Groovy scripts. > Ikai Lan > Developer Programs Engineer, Google App Engine -- 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 [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-java?hl=en.
