[SERVER-78123] cpuFrequencyMHz likely showing current frequency rather than max Created: 08/Jun/23 Updated: 01/Nov/23 Resolved: 01/Nov/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 7.2.0-rc0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Jawwad Asghar | Assignee: | Brad Moore |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | neweng | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Server Security
|
| Backwards Compatibility: | Fully Compatible |
| Sprint: | Security 2023-09-04, Security 2023-09-18, Security 2023-10-02, Security 2023-10-16, Security 2023-10-30, Security 2023-11-13 |
| Participants: |
| Description |
|
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 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. |
| Comments |
| Comment by Githook User [ 26/Oct/23 ] |
|
Author: {'name': 'W. Brad Moore', 'email': 'brad.moore@mongodb.com', 'username': 'wbradmoore'}Message: |
| Comment by Britt Snyman [ 15/Jun/23 ] |
|
Ask here is to ensure we have max CPU frequency in hostInfo. |