Request for test by users seeing 0.00 load average in spite of a busy system

[Mark Geisert]

Hi Christian,

On 10/2/2024 1:09 AM, Christian Franke via Cygwin wrote:
[...]
> Same result on Win10 22H2 (10.0.19045.4780, i7-2600K) and Win11 23H2 
> (10.0.22631.4037, i7-14700K):
> 
> $ ./test
> PdhOpenQueryW           returns PDH_CSTATUS_VALID_DATA
> PdhAddEnglishCounterW#1 returns PDH_CSTATUS_VALID_DATA
> PdhAddEnglishCounterW#2 returns PDH_CSTATUS_VALID_DATA
> PdhAddEnglishCounterW#3 returns PDH_CSTATUS_VALID_DATA
> 
> $ uname -r
> 3.5.4-1.x86_64
> 
> $ stress-ng --cpu 4 --timeout 30
> stress-ng: info:  [586] setting to a 30 secs run per stressor
> stress-ng: info:  [586] dispatching hogs: 4 cpu
> ...
> stress-ng: info:  [586] successful run completed in 30.47 secs
> 
> $ uptime
>   09:59:01 up 28 min,  0 user,  load average: 0.00, 0.00, 0.00

Thank you. I suspect most users who try the test will see the same. I 
have one system that tests differently and I hope to determine if my 
system has some problem or that there's a subset of systems out there 
that work like mine. Here's the output from my problem system...

~ ./test
PdhOpenQueryW           returns PDH_CSTATUS_VALID_DATA
PdhAddEnglishCounterW#1 returns PDH_CSTATUS_NO_OBJECT
PdhAddEnglishCounterW#2 returns PDH_CSTATUS_VALID_DATA
PdhAddEnglishCounterW#3 returns PDH_CSTATUS_NO_OBJECT

~ uname -r
3.5.4-1.x86_64

~ uptime
  19:02:08 up 6 days, 21:59,  0 user,  load average: 0.00, 0.00, 0.00

~ ./loadavg
32.00

This system is running Windows 10 21H2, build 19043.2251. It's an AMD Tr 
PRO 3955WX busy with numerical calculations.

The "./loadavg" line demonstrates a tool that I plan to release that 
gives a much more accurate load average the moment it is called. The 
uptime display still has zeroes because I haven't updated the Cygwin DLL 
on this machine yet. Awaiting more results of my call for testing :-).
Cheers,

..mark