It's all about the answers!

Ask a question

Build Forge 7 much slower than previous major releases


Tom Rochette (1644) | asked Aug 13 '11, 3:50 p.m.
Hi,

I've noticed that Build Forge 7 is much slower than previous releases when it comes to inter-steps and agent selection. It seems like there is a lot of time spent deciding which build agent should be used and then actually starting the step (such as setting up the environment) compared to the previous versions.

For instance, when you look at a job, you can see in the status "waiting", while in older releases it would seem like you were never in that waiting state.

My question is then "is there anything we can do to reduce this inter-step time" (like changing some system variables) and if my interpretation is wrong, can you point out what is actually making a single build (with the same steps) take longer on the current release (7.1.2.2) than previous releases?

Thanks

One answer



permanent link
Robert haig (1.0k16) | answered Aug 15 '11, 11:11 a.m.
FORUM MODERATOR / JAZZ DEVELOPER
previous major releases to 7 would be 3.x. BF 3.x (pre-IBM) didn't have the selector step to take, and didn't have the scaling features that 7.x does. But I don't think that apples/oranges comparison is the root of your problem.

Jobs in "waiting" status are typically not being run because of the throttling mechanisms in place on the console. "Run Queue" and "Max Console Procs" are typical culprits.

The jazz.net library article https://jazz.net/library/article/603 "Controlling Rational Build Forge resource usage through throttle mechanisms" discusses these settings and more.

As for what is making it take longer, that is more complex a discussion than is appropriate here. There are many factors. Database (network distance console, type, platform, disk type), build servers (type, network distance, number, manifest refresh rates), management console (OS, system configuration, network distance from DB and build servers) and other typical system performance variables. Typically it's that the default run queue is 3 and you're trying to run multiple jobs at a time.

I suggest read over that library article, make some adjustments, and if that doesn't solve your problem, check in with support.

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.