@89c51
Learn to codeIt's greatly useful.
@PeterKraus
If the topmost number, graphics pipe, stays low, then you're not GPU-limited. If graphics pipe is high but other numbers low, that just means even load on the units.
Heya,
that's a nice utility.
I'm just wondering - if I don't hit more than 50% in anything during "heavy load", it's probably not a GPU bottleneck, right?
Thanks,
Peter
@89c51
Learn to codeIt's greatly useful.
@PeterKraus
If the topmost number, graphics pipe, stays low, then you're not GPU-limited. If graphics pipe is high but other numbers low, that just means even load on the units.
Even if my "skills" went beyond basic understanding of pointers the problem is not "learning" to code but knowing what you want to do and how (well thats programming in its essence). And i don't know how to interact with certain stuff in a PC/Operating System. In other areas that i am more knowledgeable -stupid choices of my youth as it was proven- i can code and get things done.
It's AMD's proprietary extension exposing the performance counters, if you happen to run Catalyst. Note that the names are all obfuscated (001 002 003....) so even running Catalyst won't make that extension useful by itself.
Luckily for blob users AMD also releases a closed-source library that maps those hidden names to proper names. You can use that if you need perf counters and use the blob.
First tarball release up, 0.5.4.1. No real changes from .4, just more convenient packaging for people who don't like git.