elementary / elementary/monitor

CPU Frequency values seem to favor unused cpu than actively used ones

Open
#495 1 comment 0 reactions 0 assignees View on GitHub
Dominant language
Vala
Stars
362
Forks
49
Avg merge
10d 1h
Merged PRs (30d)
2

Description

### What Happened?

When installing the app, the values that were being shown for frequency didn't look right since my cpu runs hot due to it being constantly overclocked.

The average value being shown was around `0.6-0.9GHz` when most other metrics clock it multiples higher than that.

Image

Some ideas on how to fix this is to:
- average the frequency among threads
- average the frequency among actively used threads (currently using this locally)
- fetch the max value

### Steps to Reproduce

1. Compiled from GitHub
2. Run

### Expected Behavior

The app to show something closer to what other monitors show. My bios and windows show readings much higher.

### OS Version

Other Linux

### OS Architecture

amd64 (on most hardwares)

### Session Type

Secure Session (Wayland)

### Software Version

Compiled from git

### Log Output

```shell
# Here is a readout from what is used to get the current freq in the app in KHz
# 5668215
# 5668399
# 5615676
# 5589621
# 5645694
# 624194
# 4101926
# 4933017
# 4956825
# 3614179
# 5437545
# 5452321
# 3680064
# 5479805
# 3444413
# 5339616
# 5284446
# 5665071
# 5669509
# 5656725
# 624194
# 5647227
# 2816723
# 624194
# 624194
# 624194
# 4156778
# 624194
# 624194
# 624194
# 624194
# 624194
```

### Hardware Info

16 core AMD Ryzen 9 9950X CPU with auto-overclocking enabled in bios

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.