On 31 December 2010 02:49, Andrew DeFaria wrote: > On 12/30/2010 08:41 PM, David Antliff wrote: >> The "load average" is a bit more complicated than just how busy the >> system is - it's related to the number of processes waiting for the >> CPU, with some time-weighted averaging and a few other herbs and >> spices. I'm no Windows system programmer so I don't even know if that >> sort of information is even available to Cygwin. > > I do understand what load average is. What I'm saying is 0 is unhelpful. >> >> I 'discovered' this zero thing myself last year when I was trying to >> incorporate some sort of logging into a build system I wrote to run in >> Cygwin - I had hoped to compare 'machine load' over multiple builds >> over time, but as you know, you just get zeroes. So I just used build >> timing metrics instead (i.e. the 'time' command). Personally I >> wouldn't mind a Cygwin/Windows-specific measurement that provided some >> sort of "how busy is the machine" metric (one probably exists - >> anyone?) but I think it might be better to not overload the "load >> average" fields as they are pretty specific in their meaning. > > IMHO it's 100% better than just outputting 0's. Putting out 0's gives you no > info at all!
Bollocks. You'd be the first to complain that those stupid Cygwin devs don't even understand what an average is. The 0% tells you pretty clearly that that information is not available. >> In my opinion, I think it's better to have zero values rather than >> anything fake. A consistent and reasonable 'estimate' (if possible) >> would be OK for my purposes but I can't speak for anyone else. >> > I beg to differ. I don't see how having 0 values is better than some > approximation of load. Surely Windows has some measurement of the number of > processes in the run queue. And surely you'd be able to find it at http://msdn.microsoft.com/library. > A simple count of the number of processes with CPU usage > 0 > (minus the system idle) process would be a good start. Hardly. The challenge here is to actually collect the data for the last 15 minutes, so you'd be looking either at some sort of service process waking up frequently to sample the CPU state, or some unholy and unreliable scheme where Cygwin functions go off and do that every now and then before doing their actual job. Andy -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
