You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug Looking at the docs, it seems like it's hinting that this value changes based on load/usage because of the speedMin and speedMax datapoints. However, in all my testing across Linux and windows, laptop and PCs, that value never changes - it only shows the base CPU speed at all time, no matter load or what governor is being used.
To Reproduce
1- si.observe({ cpu: 'speed' }, 1000, (data) => console.log(data.cpu.speed))
2- Try this on Linux/Windows, underload, without, different governer.
3- See the number not change.
Expected behavior
Unclear
The text was updated successfully, but these errors were encountered:
Describe the bug
Looking at the docs, it seems like it's hinting that this value changes based on load/usage because of the
speedMin
andspeedMax
datapoints. However, in all my testing across Linux and windows, laptop and PCs, that value never changes - it only shows the base CPU speed at all time, no matter load or what governor is being used.To Reproduce
1-
si.observe({ cpu: 'speed' }, 1000, (data) => console.log(data.cpu.speed))
2- Try this on Linux/Windows, underload, without, different governer.
3- See the number not change.
Expected behavior
Unclear
The text was updated successfully, but these errors were encountered: