It's all about the answers!

Ask a question

Ant based builds are really slow. Anyone noticed this?

Karthik Krishnan (8825118163) | asked Oct 07 '13, 7:52 a.m.
ANT based builds in RTC are really slower compared to running the file directly on command prompt. Has anyone experienced 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 toolkit

One answer

permanent link
Krzysztof Kaźmierczyk (7.4k476103) | answered Oct 07 '13, 8:30 a.m.
Hi Karthik,
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.

Karthik Krishnan commented Oct 07 '13, 10:18 a.m.

Thanks for the reply. I have no Java VM arguments in the ANT section.

Karthik Krishnan commented Oct 08 '13, 2:44 a.m.

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?

Krzysztof Kaźmierczyk commented Oct 08 '13, 5:23 a.m.

Hi Karhik,
I believe that we need to check why the build is progressing slowly. Can you use WAIT Tool from to see which methods are running slowly there.
You can also consider opening new PMR to RTC support assist you in running WAIT Tools

Karthik Krishnan commented Oct 09 '13, 4:24 a.m. | edited Oct 09 '13, 4:25 a.m.

Raised a PMR. Guess something is really wrong. Thanks for the support

Nick Edgar commented Oct 27 '13, 1:59 p.m. | edited Oct 27 '13, 1:59 p.m.

I assume you're using the teamFetch task to do the load.  

I agree it's most likely due to differences in which VM or VM arguments are used.
Are you using the IBM JRE or Oracle?  One difference is that the Oracle VM has a max heap of 64M by default, whereas IBM's defaults to 1G.

Karthik Krishnan commented Nov 11 '13, 5:00 a.m. | edited Nov 11 '13, 5:01 a.m.

 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. 

Nick Edgar commented Nov 11 '13, 8:51 a.m. | edited Nov 11 '13, 8:51 a.m.

What are the differences between running directly vs running under JBE/Ant?

Is it just that the JBE based builds run the SCM accept/fetch, or are there other differences?  What amount of time is reported for the SCM phase in the build result? Does it account for the full difference? Are you running with a very large stream / build workspace?  Are the build machines running JBE co-located with the RTC server, or are they remote?

Krzysztof Kaźmierczyk commented Apr 14 '14, 3:26 a.m.

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.

showing 5 of 8 show 3 more comments

Your answer

Register or to post your answer.

Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.