Although latency affects everybody I get the sense that there are many
who are hit by the frequent cold starts to a much greater degree of
severity. So much so that it is a show-stopper for them on GAE.
Perhaps the problem could be solved early in the development process
by strongly recommending against using frameworks such as Spring
I hope that JVM level improvements such as those hinted at by JSR 121
and the IBM Cloneable JVM will allow images of a fully initialized app
to be cloned to other nodes without the need to re-initialise.
Developers and the tools they currently use expect apps to initialise
infrequently.
On 5 Mar 2010, at 09:46, Jeff Schnitzer wrote:
On Thu, Mar 4, 2010 at 6:31 PM, Robert Lancer
<[email protected]> wrote:
Jeff please watch this http://www.youtube.com/watch?v=aXJklICrFJI
That reinforces my opinion that the GAE team should spend less time
focusing on cold starts and worry more about datastore latency, which
affects *every* request.
(oh, and adding spatial indexes ;-)
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
.
--
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.
