On Thu, Mar 4, 2010 at 1:54 PM, Robert Lancer <[email protected]> wrote: > > You should join me in commenting on every pro google article on > techcrunch (they're all pro google), im basically accusing them of > being google suck ups for totally missing the app engine outage. this > is prob the only way to get the exces at google to wake up and > properly support app engine, they need some negative press for once.
Did you miss this? http://techcrunch.com/2010/02/24/google-app-engine-outage/ You're mixing together too many issues and come across sounding like the noobs who skip the documentation and clutter this list with "why won't my EJBs load?" I agree with you that datastore latency seems to be an issue. Not yet a fatal issue, but something to keep an eye on. Hopefully something that continued evolution of the datastore (or more/faster hardware) will solve. Cold start times are a separate issue. Let me say something that should be pretty obvious to anyone that thinks it for a while: THE COLD START PROBLEM WILL NEVER BE SOLVED. Google has already worked a minor miracle by creating an appserver that loads and serves pages in a second or two. If your application spends 20s loading framework, there is only one solution to this problem: Don't spend 20s loading framework. Change the way you write your applications. Yes, Google could give you the option to pay for a "warm" instance, but it will only reduce - not eliminate - cold start times. Users will still see them when you redeploy your app, when a new instance spins up to handle load, or when your instance migrates off of a hot server. GAE is not a J2EE environment. It's something different. You have to code for it in ways that J2EE devs are not accustomed to. Come to terms with this. I don't know exactly how many Googlers are working on GAE, but from the little birdies I know I gather it's not a huge team. Their resources are precious and every hour spent making fractional improvements to load times is an hour not spent filling in the vast chasm of missing features (servlet 3.0 and spatial indexes top my personal list). Presumably the "low hanging fruit" has been addressed (optimizing appserver startup time, precompilation), so further improvements will likely have a low effort-to-payoff ratio. ...which basically means your continued whining about cold start times is the reason I don't have spatial indexes. More or less. Jeff -- 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.
