Comment 1 Denis Roy 2010-07-27 10:11:02 EDT

- he is taking 97% of _one_ CPU.  That machine has four, and I just looked -- the other three are idle most of the time.

- he has properly set the nice level to 10, which means low priority

- build2 currently has 8 CPU cores that are idle, so why are you not using it?

- what do you mean by 'trying to run our build'.  Is it terminating with an error, or just taking longer than usual?

Comment 2 Paul Webster 2010-07-27 10:14:57 EDT

(In reply to comment #1)
> - build2 currently has 8 CPU cores that are idle, so why are you not using it?

Because I'm in the end game and until recently build2+eclipseSDK didn't work.  I'd imagine it's a bad idea to jiggle builds at the very end of a cycle.


> - what do you mean by 'trying to run our build'.  Is it terminating with an
> error, or just taking longer than usual?

A lot longer than usual.

PW

Comment 3 Paul Webster 2010-07-27 10:16:40 EDT

The main priority on that job is 35 (compared to 18 for our build).  How can I get up there like that (35-10 is still 25).

PW

Comment 4 Paul Webster 2010-07-27 10:19:29 EDT

(In reply to comment #3)
> The main priority on that job is 35 (compared to 18 for our build).  How can I
> get up there like that (35-10 is still 25).

bah, maybe I'm still reading it wrong.

PW

Comment 5 Denis Roy 2010-07-27 10:32:44 EDT

I guess what I'm trying to say is that you don't need to raise your process priority, since there are idle CPUs.  If you examine top, your process is only taking a few % of one CPU.  I stopped egwin's process, and a webtools process that was using the same CPU as your e4 build (but at a higher nice level) and your process _still_ only took 3-14% of one CPU.

Right now the likely bottleneck seems to be disk access to the working area (/shared).

Comment 6 Paul Webster 2010-07-27 10:41:16 EDT

Thank you for looking into this.

PW

Comment 7 Denis Roy 2010-08-03 23:41:32 EDT

I'll close this as WORKSFORME.  If you see someone taking 400% let me know.  :)