Ant based builds are really slow. Anyone noticed this?
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
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. Comments
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,
Raised a PMR. Guess something is really wrong. Thanks for the support
2
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.
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?
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,
showing 5 of 8
show 3 more comments
|
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.