I was noticing that the BZ box gets hammered, at the moment due to buildbot:
4:18pm up 89 days, 10:14, 3 users, load average: 7.00, 7.04, 7.05
PID USER PRI NI SIZE RSS SHARE STAT %CPU %MEM TIME COMMAND
26555 buildbot 20 0 9348 9348 1548 R 28.1 1.8 0:01 perl
26538 buildbot 16 0 11288 11M 1724 R 27.5 2.1 0:01 perl
26490 buildbot 14 0 15504 15M 1920 R 26.9 3.0 0:05 perl
26520 buildbot 14 0 23820 23M 13212 R 24.4 4.6 0:02 perl
26563 buildbot 20 0 23552 23M 14248 R 24.4 4.5 0:01 perl
26561 buildbot 20 0 23536 22M 13432 R 18.9 4.5 0:00 perl
15982 jm 17 10 21576 1672 1660 R N 12.6 0.3 1738m mass-check
26521 buildbot 14 0 23356 22M 14460 R 11.4 4.5 0:00 perl
26562 buildbot 9 0 22968 22M 15448 S 8.4 4.4 0:00 perl
If we're going to run buildbot on there, it should at least be done in serial
and not parallel.
I'm also not sure that it's the best box for a mass-check either, but they're
having issues at the moment it looks like:
jm 9449 9408 0 Jan15 ? 00:00:13 /usr/bin/perl -w ./mass-check --
jm 15976 9449 0 Jan15 ? 00:12:40 /usr/bin/perl -w ./mass-check --
jm 15977 9449 0 Jan15 ? 00:14:03 /usr/bin/perl -w ./mass-check --
jm 15978 9449 0 Jan15 ? 00:13:05 /usr/bin/perl -w ./mass-check --
jm 15979 9449 0 Jan15 ? 00:17:06 /usr/bin/perl -w ./mass-check --
jm 15980 9449 0 Jan15 ? 00:12:44 /usr/bin/perl -w ./mass-check --
jm 15981 9449 0 Jan15 ? 00:11:12 [mass-check <defunct>]
jm 15982 9449 77 Jan15 ? 1-04:59:08 /usr/bin/perl -w ./mass-check
jm 15983 9449 0 Jan15 ? 00:11:09 [mass-check <defunct>]
jm 22210 15978 0 Jan15 ? 00:00:00 [dccproc <defunct>]
jm 22211 15982 0 Jan15 ? 00:00:00 [dccproc <defunct>]
--
Randomly Generated Tagline:
He gets it from your side of the family, you know. No monsters on my
side.
-- Homer Simpson
Treehouse of Horror II
pgpAXTT4x59Ox.pgp
Description: PGP signature
