-
Type:
Task
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: None
-
Server Security
-
Fully Compatible
-
Security 2023-09-04, Security 2023-09-18, Security 2023-10-02, Security 2023-10-16, Security 2023-10-30, Security 2023-11-13
-
None
-
0
-
None
-
None
-
None
-
None
-
None
-
None
In the Info section of t2 data, within the hostInfo section, the cpuFrequencyMHz value seems to be showing the current CPU frequency rather than the max CPU frequency.
I would think the max frequency of the processor would be the relevant metrics for this section.
I looked at cpuFrequency across several M200-NVME atlas variant runs and saw values of 1932.342, 2156.250, 2530.926, and 2734.478 which led me to this conclusion based on the wide range of values, and how non-whole they are.
Also, for t2 data from ARM standalone variants, the cpuFrequencyMHz was blank.