Hi,
kullervo was trying to build curl again, and like the previous build, it
timed out in test 518. I tried to renice some processes with htop, but the
test processes were using only very little CPU time. The most time, besides
top, was used by jbd2/dm-4-8, which seems to be related to the ext4 fs. Is
this really slowing down the build? Is there a way to fix this? Do we really
need journalling on a filesystem that is thrown away after every build? Any
tuning ideas? Or maybe curl should skip the tests, as the build itself seems
to work fine?
top - 22:59:32 up 22 days, 8:20, 3 users, load average: 3.23, 3.45, 3.37
Tasks: 117 total, 1 running, 108 sleeping, 0 stopped, 8 zombie
%Cpu(s): 67.5 us, 0.0 sy, 0.0 ni, 0.0 id, 0.0 wa, 32.5 hi, 0.0 si, 0.0 st
KiB Mem: 109576 total, 107688 used, 1888 free, 34588 buffers
KiB Swap: 2096092 total, 29304 used, 2066788 free, 25460 cached
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
32092 root 20 0 5140 1304 928 R 40.9 1.2 0:01.75 top
5662 root 20 0 0 0 0 D 21.0 0.0 362:06.30 jbd2/dm-4-8
13992 buildd 5 -15 5660 516 136 D 6.0 0.5 64:21.66 lt-lib518
31554 root 20 0 0 0 0 S 1.8 0.0 0:18.62 kworker/0:0
3 root 20 0 0 0 0 S 1.2 0.0 21:40.46 ksoftirqd/0
1 root 20 0 2004 76 44 S 0.0 0.1 1:19.49 init
2 root 20 0 0 0 0 S 0.0 0.0 1:23.83 kthreadd
Christian
--
To UNSUBSCRIBE, email to debian-68k-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20130421211953.ga18...@chumley.earth.sol
