Ant based builds are really slow. Anyone noticed this?
Rough build times
via ANT -> ~1hr 10 mins, direct call -> ~20 mins
on Windows 7 64 bit, 12 core, 32 GB RAM, SSD, ANT 1.8.2 & ant contrib 1.0b3
We are on RTC 4.0.2 server and build toolkitOne answer
It might be an issue that you have different VM arguments when running from Jazz.
Please check and provide Java VM arguments in Ant section of your build definition.
Comments
Thanks for the reply. I have no Java VM arguments in the ANT section.
Do I need to specify any Java VM arguments to make the builds faster? also we have around 30 build definitions. Do I need to specify the same in all the build defs?
Hi Karhik,
I believe that we need to check why the build is progressing slowly. Can you use WAIT Tool from https://wait.ibm.com/ to see which methods are running slowly there.
You can also consider opening new PMR to RTC support assist you in running WAIT Tools
Raised a PMR. Guess something is really wrong. Thanks for the support
I assume you're using the teamFetch task to do the load.
2 votes
Hi Nick, Sorry for delayed response. We use the RTC to load the stuff (RTC builds out-of-the-box), but the build (calling batches etc) is done via ANT. We use Oracle JRE.
What are the differences between running directly vs running under JBE/Ant?
Hi Karthik,
I go a bit more information about what you are doing:
You are running MakeFile script via ant task using RTC ant build definition. Can you confirm that? If that is true:
1. As you are using Makefile script, the natural way to run it in RTC
is using command line build definition, not ant build definition. What
is the reason you use ANT here?
2. I would like you to compare running times for two following cases:
2.1. You run build using jbe
2.2. You start ant build file on the same machine
2.3. You start make script
When running these 3 cases we can determine what is exactly bottleneck
here: whether it is ant or it is an issue with jbe.