A couple hours later, all is well. Instances are lasting. Latency is low. Thank you Mr. Sparkles. (burp).
On Wednesday, February 27, 2013 6:45:50 PM UTC-7, Cesium wrote: > Oh Joy, > > Now the console charts have been erased. > > I'm losing it. > > Unicorn liver pate for dinner. > > David > > > > On Wednesday, February 27, 2013 6:10:37 PM UTC-7, Cesium wrote: > > Starting about 16:30 Pacific time, my Java HRD Instances were shutting down > > after just a few seconds. > > > > Just as my rage reached class IV, serving returned to normal. > > > > I know this is an overreaction, but I may have to sacrifice a unicorn. > > > > Please, please, App Engine team, spare Mr. Sparkles. > > > > > > This is disheartening, > > David > > > > On Wednesday, February 27, 2013 11:32:07 AM UTC-7, Chris Tan wrote: > > > I'm also getting this problem. > > > > > > On Wednesday, February 27, 2013 7:50:47 AM UTC-8, Kinesh Patel wrote:On > > > Python 2.7 paid app. Setting an idle instance seems to mitigate this, but > > > every time a new dynamic instance is spawned or hit i get this problem. > > > Definitely not normal behavior. -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-appengine+unsubscr...@googlegroups.com. To post to this group, send email to google-appengine@googlegroups.com. Visit this group at http://groups.google.com/group/google-appengine?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
