First of all: Thank you very much for all the feedback!

This build I am trying to optimize is compiled on our build server by
the continuous integration tool (hudson in our case triggered after
every commit). It is mainly used to run unit tests and for general
testing by the developers to get "instant" feedback (well, it used to
do that when we started). It is not a production build. But I don't
like to take too many things out, e.g. take out browsers then you can
no longer test it on different browsers and your feedback cycle - the
time until you notice something doesn't work after you implemented it
- gets longer). For the production build then it is absolutely OK to
take longer.

I tried using the draftCompile switch and it already reduces the build
time to 53minutes - that's a huge 25% decrease compared to the
previous 1h12min.

I will try to play with the optimize level now.

Regarding the SSD: This is not really an option for me as the build is
running on a server used by other projects/users so that would be a
major operation.

Please let me know if you have any other suggestions.

Dennis

On May 18, 8:47 pm, Sanjiv Jivan <[email protected]> wrote:
> Have you tried compilation using SSD? I'm my experience from last year,
> SSD's were great for reads but terrible for writes and compilation of medium
> to large projects actually took a fair bit longer on SSD's.
>
> It's possible the newer SSD's have gotten better but I would recommend doing
> some more research before making this expensive purchase with expectations
> of significant compile time speed improvements.
>
>
>
>
>
>
>
> On Wed, May 18, 2011 at 2:22 PM, Jeff Larsen <[email protected]> wrote:
> > What is the purpose of the build?
>
> > Is it to deploy the actual code to a production/test server or is it to
> > enable some sort of selenium/webdriver test framework.
>
> > If it is the latter, you could add -draftCompile which will not be highly
> > obfuscated code, but it should be a quicker compile, especially with 48
> > perms.
>
> > You could also link up multiple computers to do distrubted permutation
> > computations. Ray Cromwell had a talk about this at last year's IO.
>
> > Depending on your budget, a SSD drive could potentially help you out a lot
> > here too.
>
> > --
> > You received this message because you are subscribed to the Google Groups
> > "Google Web Toolkit" 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-web-toolkit?hl=en.

-- 
You received this message because you are subscribed to the Google Groups 
"Google Web Toolkit" 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-web-toolkit?hl=en.

Reply via email to