Hello,
@KGIII ! Good to "see" you again. No, I didn't set any such thing. And I don't know how to. Ha! Thank you! Where would I set/clear that?
The value of 799MHz as average for the cpu frequency shouldn't be a problem on the machine. This machine here from which I'm writing runs just that frequency without any issues of latency. To check the current frequency of all the cores of the cpu one can run the following:
Code:
[~]$ grep -iE 'processor| mhz' /proc/cpuinfo
processor : 0
cpu MHz : 800.000
processor : 1
cpu MHz : 800.000
processor : 2
cpu MHz : 800.000
processor : 3
cpu MHz : 800.000
processor : 4
cpu MHz : 800.000
processor : 5
cpu MHz : 800.000
processor : 6
cpu MHz : 800.000
processor : 7
cpu MHz : 800.000
processor : 8
cpu MHz : 800.000
processor : 9
cpu MHz : 800.000
processor : 10
cpu MHz : 796.627
processor : 11
cpu MHz : 800.000
processor : 12
cpu MHz : 800.013
processor : 13
cpu MHz : 800.000
processor : 14
cpu MHz : 800.000
processor : 15
cpu MHz : 800.000
processor : 16
cpu MHz : 800.000
processor : 17
cpu MHz : 799.953
processor : 18
cpu MHz : 800.000
processor : 19
cpu MHz : 800.000
One cpu, processor 10 in this case, runs less than 800MHz, which would bring the average down to 799MHz. Another, cpu 17 also helps in that respect.
To check the frequency range of the cpu one can run:
Code:
[~]$ cpupower frequency-info
analyzing CPU 13:
driver: intel_pstate
CPUs which run at the same hardware frequency: 13
CPUs which need to have their frequency coordinated by software: 13
energy performance preference: balance_performance
hardware limits: 800 MHz - 3.50 GHz
available cpufreq governors: performance powersave
current policy: frequency should be within 800 MHz and 3.50 GHz.
The governor "powersave" may decide which speed to use
within this range.
current CPU frequency: Unable to call hardware
current CPU frequency: 800 MHz (asserted by call to kernel)
boost state support:
Supported: yes
Active: yes
The range is shown as "hardware limits: 800 MHz - 3.50 GHz", and the current policy allows the full range to be used. If the current policy shows a level of frequency lower than the hardware limit, it's been capped, which restricts its functionality. There are circumstances in which a user may wish to do that, but perhaps not in this case.
If the above details are in order, then the latency may not be cpu related.
On the htop output in post #48, the cpu activity is absent from the top of the htop details. It may have been cropped out. The default for htop is to show the cpu activity, as seen in the following image. To return to the default, one can remove the htop config file at ~/$USER/.config/htop/htoprc, and next time htop is opened it should restore the default config file.
. Fortunately I had some hard drives ordered and already on their way. It's a pity about this bad hard drive - it was a 1 TB drive.
