the following should be the % utilization of logical core #65 on physical CPU 1 (or logical core #193) ![]() the following should be the % utilization of logical core #65 on physical CPU 0 the following should be the % utilization of physical CPU 1 across all its 128 logical cores the following should be the % utilization of physical CPU 0 across all its 128 logical cores the following should be the % utilization across all 256 logical cores In other words, it isn't a Rainmeter thing, at least if you use UsageMonitor to get a specific counter (not sure about the CPU measure though). At least this is what appears to be the reasoning in the 1st link from the 2nd answer posted there. Apparently the "old" Perfmon counters under "Processor" are limited to a maximum of 64 logical CPUs, while the "new" ones under "Processor Information" should work over that limit. I have what might be an explanation as to why this happens - take a look here, especially the 2nd answer. Ultimately, this is going to be difficult to solve unless one of the team members has access to a machine like this. The MS docs do mention logical processor "relation groups", however it is unclear if this has anything to do the problem at hand. There is nothing in the MS docs that suggest there is any limitation. In both cases, Rainmeter asks Windows (via the winapi) for that information. Rainmeter does not explicitly restrict the number of logical CPU's that can be referenced (both in UsageMonitor or the CPU measure). It's hard to tell where the problems lies. Here's a simple skin that shows the issue using both measure methods:īrian wrote: ↑ February 7th, 2021, 9:05 am Aside from existing servers, I'm pretty sure there will be PC/Workstation systems in the wild at some point soon with >64 logical cores. While the above processor is a server-class device, you can already buy AMD Threadripper Processors with 64 logical cores. Is the issue with the UsageMonitor also a known bug/limitation? Can this be fixed soon? Is there a workaround without using say the HWInfo plugin (haven't tried it yet so don't know if works but would prefer not have to install this tool)? I assume CPU Measure is a known limitation given the error. I have found that as soon as I attempt to measure a CPU above 64, the usual CPU Measure throws an error in the log "CPU: Processor=65 is not valid" and while UsageMonitor doesn't throw any errors I can see, it simply does not work for Name=>64. Everything is explained in the link above.I'm writing a skin to monitor each CPU core on a dual AMD EPYC 7742 64-Core Processor. Some variables may need an update for your particular config using HWinfo. The skin is working for an AMD Ryzen CPU and MSI b450 motherboard.Fraps should be started before HWinfo, otherwise the variable are not available.Fraps and HWinfo have to run in the background. ![]() If you want to use the skin, do NOT update to 7.0. I will not provide an update yet, as compatibility between users is heavily impacted and requires a lot of modifications for you to use it properly. Since HWInfo 7.0 update, the skin won't work. Fraps variable are available in HWinfo once the software installed. This will provide you with your hardware IDs and you just have to update the skin with them.įor FPS, you have to install Fraps. If you need to update sensors values for you hardware, you will find in Ressources folder of the skin HWiNFOSharedMemoryViewer.exe. Please refer to the following link for instructions on HWinfo: /raiguard/ModernGadg… It uses only one monitoring software in the background, HWInfo. Here is an example on my 7" screen: /a/dsA56uw I created a simplified Dashboard skin for Rainmeter to monitor CPU, GPU and FPS.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |