Ever since I ported our app to Go, we have had no trouble with the scheduler aggressively recycling dynamic Java instances (because we have none). This may be due to the Go runtime depending on Mermaids instead of Unicorns and Skittles like the Java stack.
On Monday, April 1, 2013 5:58:05 AM UTC-7, Cesium wrote: > > Dearest Rafael, > > You are living in a dream world if you think migrating to HRD will stop > instances from dying prematurely. > > This is not a criticism! Purposeful rejection of reality will save you! > > Do not apply reason to the instance scheduler! Here, we call it a > "faith-based" scheduler. > > Have you not read any of the other posts on this issue??? > > Is it not definitive proof of the validity of my faith that the almighty G > has not spoken to us about this problem? > > (Should have posted this on Easter.) > > David > > > -- 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 [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/google-appengine?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
