I have a large GWT app with over 50 complex data entities with very complicated relationships between them. There are over 100 RPC methods, and I use various GAE services (Users, Memcache, Blobstore, Images, and Mail). My new instance startup time ranges from 4 to 5 sec on F1. Sometimes it goes a little higher. The lowest was 3.6 sec. I use the low-level API and no DI. Productivity tools are nice, but they have their cost.
In any case, if Jeff's suggestion is implemented (dispatch only to warm instances), it would not matter if the start up time is 4 sec or 40. I followed this discussion closely, and to me it is obvious that the existing GAE mechanism is inferior to what Jeff is proposing (for any number of instances). There may be a good technical reason why the GAE team chose their current implementation. It is also possible that GAE was built by engineers who did not think in terms of web user experience, and who believed that a rare 30 seconds delay is the acceptable price to pay for some other benefits of the current implementation. This proposal was already starred by many people (issue 7865). It would be nice if the GAE teams takes another look and tells us whether we should expect any changes. I am sure a lot of app developers would like to know whether they should optimize for fast cold starts. These optimizations are expensive (both in direct development time and in lost productivity), so this is not an idle question. -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To view this discussion on the web visit https://groups.google.com/d/msg/google-appengine/-/VsYwv3Sf52wJ. 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?hl=en.
