Actually, I just noticed that not only are the load times shorter/ gone, but my hourly cron is no longer timing out like it was. That cronttab is SO simple - it just loads up a sharded counter, then kicks off a task, but it would die from 30 second timeout about 15% of the time the past week, but since the outage, no problems.
On Feb 26, 1:11 pm, "Ikai L (Google)" <[email protected]> wrote: > No, the outage wasn't related to a performance upgrade. There are any number > of reasons why your application isn't being cycled out. I'm curious as to > whether other users see this or if they see the opposite effect. > > > > > > On Fri, Feb 26, 2010 at 9:13 AM, Blake <[email protected]> wrote: > > I was seeing 7 second load times for my first request back into the > > system after the JVM (must have) went to sleep. Now it's super fast, > > as if the JVM wasn't sleeping. This is really great. > > > Is anyone else seeing this too? I wonder if the outage was a side > > effect of a big performance push. > > > -- > > You received this message because you are subscribed to the Google Groups > > "Google App Engine" group. > > To post to this group, send email to [email protected]. > > To unsubscribe from this group, send email to > > [email protected]<google-appengine%2Bunsubscrib > > [email protected]> > > . > > For more options, visit this group at > >http://groups.google.com/group/google-appengine?hl=en. > > -- > Ikai Lan > Developer Programs Engineer, Google App > Enginehttp://googleappengine.blogspot.com|http://twitter.com/app_engine -- You received this message because you are subscribed to the Google Groups "Google App Engine" 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?hl=en.
