Quantcast
Viewing all articles
Browse latest Browse all 1137

Help: Rainmeter Skins • Re: Usage Monitor Plug-in and Roundlines/Dedicated GPU Process Memory Usage/Having Trouble With the Values.

Thanks Yincognito, I'll back to you on that, I may have bit off more than I can chew. The entire quest might be put on hold or scrapped all together.
My goal to have the most accurate MSI GPU skin may be a futile attempt, so I'm re-thinking what I got myself into, thanks.
Not necessarily, you don't have to be that pessimistic. For me, after making the code like this (disregard the meters, just look at the measure values in the log in this rudimentar sample; at the left is PerfMon.exe after adding all related counters for this):

Code:

[Rainmeter]Update=1000AccurateText=1DynamicWindowSize=1BackgroundMode=2SolidColor=128,128,128,255SkinWidth=300SkinHeight=300---Measures---[GPU0MemoryUsage]Measure=PluginPlugin=MSIAfterburner.dllGPU=0SourceId=49[GPUAdapterMemoryDedicatedUsageTotal]Measure=PluginPlugin=UsageMonitorCategory=GPU Adapter MemoryCounter=Dedicated UsageIndex=0[GPULocalAdapterMemoryLocalUsageTotal]Measure=PluginPlugin=UsageMonitorCategory=GPU Local Adapter MemoryCounter=Local UsageIndex=0[GPUNonLocalAdapterMemoryNonLocalUsageTotal]Measure=PluginPlugin=UsageMonitorCategory=GPU Non Local Adapter MemoryCounter=Non Local UsageIndex=0[GPUProcessMemoryDedicatedUsageTotal]Measure=PluginPlugin=UsageMonitorCategory=GPU Process MemoryCounter=Dedicated UsageIndex=0[GPUProcessMemoryLocalUsageTotal]Measure=PluginPlugin=UsageMonitorCategory=GPU Process MemoryCounter=Local UsageIndex=0[GPUProcessMemoryNonLocalUsageTotal]Measure=PluginPlugin=UsageMonitorCategory=GPU Process MemoryCounter=Non Local UsageIndex=0---Meters---[GPU0Roundline3]Meter=ROUNDLINEStartAngle=0RotationAngle=(PI*2)LineColor=255,216,0,100LineWidth=6.0LineLength=55LineStart=50X=150Y=150AntiAlias=1Solid=1Group=Details
GPUMemory.jpg
it became obvious that, in my case, the memory usage reported by MSI AB precisely equals the value for the luid_0x00000000_0x0000FB33_phys_0 instance name from Performance Monitor > GPU Adapter Memory > Dedicated Usage (divide the 173580288 Bytes to 1024 x 1024 and you'll get 165.53906 MBytes), or, put in UsageMonitor options:

Code:

[GPU0AdapterMemoryDedicatedUsageTotal]Measure=PluginPlugin=UsageMonitorCategory=GPU Adapter MemoryCounter=Dedicated UsageName=luid_0x00000000_0x0000FB33_phys_0
So, if I sum up the Performance Monitor > GPU Adapter Memory > Dedicated Usage for all the pid_NNNN_luid_0x00000000_0x0000FB33_phys_0 instance names (i.e. the sum of all processes having a NNNN process ID that belong to the luid_0x00000000_0x0000FB33_phys_0 adapter or video card) in the screenshot, I should get the same 165.53906 MBytes.

Now, of course, for you that luid_... might differ, but should be the same principle. How to identify that luid_... or how to sum up only values for the instance names ending in that luid_..., that's another matter as you'd probably need to use some sort of wildcards / whitelist in the UsageMonitor options, if that's even entirely possible. Regardless of how you'd attempt to do it (if you do, that is), things will then make sense.

That's exactly what I said earlier, it isn't that your skin is not accurate (since, after all, it does accurately present the retrieved data), it's just that it lacks a bit of coherence so that the value(s) you measure in [GPU0MemoryUsage] match what you measure in [GPU0AdapterMemoryDedicatedUsageTotal] above (or your individual process values), that's all. Image may be NSFW.
Clik here to view.
;-)

Statistics: Posted by Yincognito — Yesterday, 4:51 pm



Viewing all articles
Browse latest Browse all 1137

Trending Articles