On Wed, Jul 25, 2012 at 8:42 PM, David Hardwick <[email protected]> wrote: > > Amazing, Andrei. If you can get those startup times going with GWT and the > complexities you mentioned in your app, then clearly stripping out DI and > using low-level API (and likely jar'ing everything) is a mega contributor to > reducing startup time. I would hate to have to spend the team's time > stripping that stuff out, i would just pay for higher idle instances until > request #7865 gets implemented.
I just want to put this in proper perspective - we should expect Andrei's app to startup quickly. GWT-RPC is actually great for startup time because there is only a single backend servlet to start up; there's no need to build a sitemap by loading classes and looking for annotations (ie, JAX-RS). Similarly, the low-level API has zero startup overhead. Jeff -- You received this message because you are subscribed to the Google Groups "Google App Engine" 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?hl=en.
