***: dj_goku has quit IRC (Changing host)
dj_goku has joined #arpnetworks
dj_goku has quit IRC (Ping timeout: 268 seconds)
RandalSchwartz has quit IRC (Ping timeout: 258 seconds)
dj_goku has joined #arpnetworks
dj_goku has quit IRC (Ping timeout: 260 seconds)
dj_goku has joined #arpnetworks
dj_goku has quit IRC (Ping timeout: 260 seconds)
dj_goku has joined #arpnetworks
dj_goku has quit IRC (Changing host)
dj_goku has joined #arpnetworks
dj_goku has quit IRC (Ping timeout: 245 seconds)
qbit has quit IRC (Quit: WeeChat 1.7.1)
qbit has joined #arpnetworks
plett has quit IRC (Ping timeout: 260 seconds)
dj_goku has joined #arpnetworks
plett has joined #arpnetworks
dj_goku has quit IRC (Ping timeout: 240 seconds)
johnny-o has quit IRC (Remote host closed the connection)
dj_goku has joined #arpnetworks
dj_goku has quit IRC (Changing host)
dj_goku has joined #arpnetworks
dj_goku has quit IRC (Ping timeout: 272 seconds)
hive-mind has quit IRC (Remote host closed the connection)
hive-mind has joined #arpnetworks
dj_goku has joined #arpnetworks
dj_goku has quit IRC (Changing host)
dj_goku has joined #arpnetworks
dj_goku has quit IRC (Ping timeout: 272 seconds)
johnny-o has joined #arpnetworks
dj_goku has joined #arpnetworks
dj_goku has quit IRC (Ping timeout: 260 seconds)
dj_goku has joined #arpnetworks
dj_goku has quit IRC (Changing host)
dj_goku has joined #arpnetworks
dj_goku has quit IRC (Ping timeout: 240 seconds)
pyvpx_ has joined #arpnetworks
pyvpx has quit IRC (Read error: No route to host)
caseyandgina has quit IRC (Ping timeout: 272 seconds)
caseyandgina has joined #arpnetworks
dj_goku has joined #arpnetworks
dj_goku has quit IRC (Ping timeout: 260 seconds) nathani: is it normal to have a load average of 1 on a dual cpu box, even though the CPU is at 99-100% idle? Lefty: I dunno about normal, but it's not necessarily indication of a problem
load average of 1 just means there's 1 process in the run queue mkb: it is on openbsd now
some change in how kernel threads are counted mike-burns: OpenBSD's load average metric changed. staticsafe: (also on Linux, load average is not just CPU usage)
it can be disk I/O and other I/O as well mercutio: linux's load average going up is normally disk
the number of processes in D state each add 1 to the load average
at least that tends to be what it is ime
with modern cpu's it is harder to be cpu bound
at least enough to lead to checking out a high load average ***: dj_goku has joined #arpnetworks
dj_goku has quit IRC (Changing host)
dj_goku has joined #arpnetworks
dj_goku has quit IRC (Ping timeout: 260 seconds) nathani: Would the Thunder cloud contribute to the load average
Disk being network rather than local mercutio: it shouldn't be too bad
running a lot of processes at once that wait on disk i/o will increase the number ***: dj_goku has joined #arpnetworks
dj_goku has quit IRC (Changing host)
dj_goku has joined #arpnetworks
dj_goku has quit IRC (Ping timeout: 240 seconds)
dj_goku has joined #arpnetworks
dj_goku has quit IRC (Changing host)
dj_goku has joined #arpnetworks
dj_goku has quit IRC (Ping timeout: 240 seconds)
dj_goku has joined #arpnetworks
dj_goku has quit IRC (Changing host)
dj_goku has joined #arpnetworks
dj_goku has quit IRC (Ping timeout: 260 seconds)