In message: <20050221223518.GA25518_at_VARK.MIT.EDU> David Schultz <das_at_freebsd.org> writes: : On Mon, Feb 21, 2005, David G. Lawrence wrote: : > > No, disk I/O sleeps is not involved. : > > : > > The loadavg is the length of the runqueue. Any process sleeping, : > > on network, disk or timer, is not counted towards the total. : > : > I said "historically". :-) : > This was changed in FreeBSD a some years ago. : : Even further back in history, TENEX computed the load average : based on runnable jobs. :-P See footnote 1 of RFC 546. I was once told, but never went and looked at the source, that the load average on TOPS-20 was computed as 'the number of milliseconds a job had to wait for 1 millisecond of time'. The TOPS-20 scheduler let you do things like say 'this class of people get all the time they want' and 'that class of people can use no more than 10% of the CPU when the load is over 3' and the like. So the different classes might only have one or two jobs in the run queue, but still have a load average of 125! Of course, if you were in one of the bad classes, then it could take 15 minutes to get enough time to type 'uptime'. But this is getting a little far afield... WarnerReceived on Tue Feb 22 2005 - 04:05:58 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:38:28 UTC