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
p
> Date: Mon, Dec 14, 2009 at 10:19 AM
> Subject: [appengine-java] Re: What does
>
> true do?
> To: Google App Engine for Java
>
> Whenever I attempt to use pre-compilation I receive a 503 Service
> Unavailable error and a roll back is made. There is no further
> expl
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)" 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 Ap
Please send us your app-id privately (if you don't feel comfortable posting
it publicly), and we can investigate.
-- Forwarded message --
From: Philip
Date: Mon, Dec 14, 2009 at 10:19 AM
Subject: [appengine-java] Re: What does
true do?
To: Google App Engine for Java
Whene
Whenever I attempt to use pre-compilation I receive a 503 Service
Unavailable error and a roll back is made. There is no further
explanation in the logs. I made several tries at different times.
Unable to update:
java.io.IOException: Error posting to URL:
http://appengine.google.com/api/appversi
