Ah, so wtpBuild is in fact the only one who is nice (aside from the
jarsigner) ?
- thomas
On 03/17/2010 06:51 PM, Denis Roy wrote:
You're seeing "15" as the nice value, not -15. Only
root can lower the nice value beyond zero.
Denis
On 03/17/2010 01:38 PM, Thomas Hallgren wrote:
While I'm
at it, I should also complain about this:
21771 wtpBuild 30 15 583m 89m 7408 S 145 0.6 0:23.77 java
Perhaps wtpBuild was inadvertently started with a negative nice value,
i.e., nice -n -15? The effect of that is that it's not so nice :-). It
tries to steal all resources that are available.
- thomas
On 03/17/2010 06:32 PM, Thomas Hallgren wrote:
Over the last couple of weeks, I've done a
'top' from time to time when I feel that my builds take longer then
they should. Very often, I see this at the top:
12252 egwin 20 0 668m 168m 11m S 115 1.1 0:09.27 java
A hint to egwin and others that run very heavy builds. The message of
the day on the build machine states:
"If you run continuous builds, you should start your shell processes
with nice -n 10 (command) to be kind to others."
Another entry that isn't that uncommon at the top is:
29702 hudsonbu 17 0 584m 101m 7372 R 124 0.7 0:25.09 java
which of course raises the question, why isn't Hudson running its jobs
with nice -10?
The jarsigner seems to be one of the few that actually does this, and
my builds always waits _very_ long times for it to complete.
Regards,
Thomas Hallgren
_______________________________________________
_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
|
