The tradeoff is a slightly longer deployment time, although in most cases it won't be noticeable and it will save you a significant amount of CPU time during loading requests.
Precompilation will be turned on by default in a future release, but we're still working on optimizing the performance and stability of the precompiler backend before we do that. On that note, can anyone in this thread who experienced problems with precompilation please email me (privately) a WAR file containing their deployment directory? I can verify that there are no bad files that precompilation is choking on, and work on tuning the parameters that we use for dividing your code into individual chunks. Thanks, Don On Mon, Dec 14, 2009 at 5:19 PM, David Fuelling <[email protected]> wrote: > Is there any drawback to using precompilation? Just wondering why > it's opt-in for now. > > david > > On Dec 7, 11:18 pm, "Ikai L (Google)" <[email protected]> wrote: > > It's still opt-in, so you'll need to enable it if you want it. > > > > -- > > 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]<google-appengine-java%[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.
