please stop trying to make it look like a bunch of people regularly have to beat me for [using CPU usage as a measuring device].
So I will keep this short and future-applicable.
As Hodgman said, CPU usage is basically irrelevant. Performance is measured in time, which means doing as he said and timing how long things take.
Even in your reply you mention nothing about actual timing. What you describe sounds as though it is nothing but your feeling.
So I asked you a very specific question. How do you know what changes in performance you are getting? It should be very simple to say, “I timed it using QueryPerformanceCounter(),” if that is what you did. Instead, once again, you ranted about nonsense, cluttered up your own topic, threw around accusations, and ultimately I still don’t even have an answer. How do you know if it is faster? How hard can it be to answer that? Did you time it or did you feel it?
Why can’t you give specifics and just answer the question?
also, i'm not really sure what field of expertise you have,
Primarily video games.
but in audio dsp, generally "faster" means a routine is using *less* cpu resources, and "slower" means it is using more.
There is no direct correlation between CPU usage and overall performance.
When the operating system decides that a thread or process needs more resources (based on priority levels, how often it returns control back to the operating system (for example waiting for a Windows message), accesses disk, etc.) it will give it more (and longer) time slices (which increases CPU usage), which means it has more time to run, which means its performance increases.
When your application’s CPU usage is low, it means most of the CPU power is spent on other processes or just idling, which generally implies your process is not performaning at full potential.
If your process does the exact same task at 8% vs at 92%, the 92% version will finish much faster (and you could call this “high performance”).
Since it also depends on many variables, including process priority, thread affinities, thread priorities, disk access, OS returns, waits, sleeps, yields, etc., it is a very very poor way to measure the “performance” of an application.
It’s only practical use is to let you know you are draining the battery of a laptop faster or to know if you are taking resources from other processes, which may not be desirable for applications related to audio (until the final export), but that isn’t called “performance”, that is just called a “resource hog”.
i don't think it should be necessary to dredge up my past in all of my posts, but unless i do it, how are you able to understand that i may be a "bigger person" than you are giving me credit for?
I don’t need to understand your social standing, I need to know what you want to ask and any relevant details that would help me provide an answer.