On Tuesday, March 12, 2013 12:18:24 PM UTC-5, Carl Schroeder wrote: > > The sentiment is not anti-Java, it is anti GAE/Java. Writing "Hello world" > to the datastore takes 4-5 seconds to cold start load on an F2 in GAE/Java. > That is on good days, it could take twice as long on stormy days. The more > the application grows, the worse this gets. > > Why risk 5+ second response times? Wait until Google has fixed the Java > instance loading time issue before you embark on writing Java apps for GAE. > FYI, I used the low-level API and no frameworks. Latency was untenable. > > I can't say that I share your experiences with GAE/J, I find that I can routinely cold start instances + datastore requests in less than 5 seconds, although I'm recently having issues with memcache slowness...
True, GAE/J has problems. But so do the Python and Go runtimes. I'm subscribed to the google-appengine-go Google group, and I see as many complaints there, as I do on this group about Python/Java. Giving the OP a balanced view of the pros/cons of each runtime is the point of this thread, and I think it's fair to let him know what he's looking at. @OP: if you're interested in looking more about Java performance, may I recommend this thread (it's a bit of a long read, to give you fair warning): https://groups.google.com/d/msg/google-appengine/sA3o-PTAckc/okDqu5aE-78J -- 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.
