Experience Index (or a better name than Windows uses)

[sephult]

I am wondering if there possibly could be some method in the future to come up with a generic numbering system, or method similar to how Windows has it's Experience Index that we could use for the add-ons.
I have built (and am building some complex patches, and in some cases others might not be able to run them (as was experienced quite recently with nay).

I know CPU is the best way to judge for your local system, however this does not translate well when trying to compare with others.
It becomes difficult to design a patch that can be shared with the community, without understanding how it might run on other systems.

Quite possibly is there any manner to retrieve any more CPU/ram or other information and derive a generic index based on last CPU per the patch design and generate a number?

Just throwing some ideas, but in this area it is difficult to design cross-community patches that are consistent on different systems. It is very hard to understand how to design to a slower computer. I think at 13% one time was maxing out on nays.


I know this is not a quick implementation, however maybe others have some ideas or could prompt a discussion regarding.


-s

[senso]

the real performance of Usine depends more on the quality of the audio driver than the CPU itself.
Some computers car have 90% of CPU without problem and some start to crackle at 30%
So this "index" is hard to estimate.