3 ms·
Performance is a combination of a) required behavior, b) implementation. If an implementation does not correctly meet the requirements, its performance cannot b
by ComputerGuru 3y ago
Performance is a combination of a) required behavior, b) implementation. If an implementation does not correctly meet the requirements, its performance cannot be compared to one that does.
- taeric 3y agoClose. Performance is also part of your "a", there. And you have to adjust implementation accordingly. Is why nobody says that old "3d" games like Doom were poorly implemented. Even if they were not fully 3d.
- ComputerGuru 3y agoSure. But I'm approaching this from the assumption that we're actually talking "observed/resultant performance" and not "baseline required performance," i.e. talking about "'excess' performance over the required threshold," and if that regresses due to a correctness issue, I don't see the problem. Now what is "the minimum required performance threshold," I cannot say, but it is surely at least the ability to render on "CPU" at 60Hz. (which CPU? render what? using how much of the available CPU power? with how many frames of latency allowed?) Note that I don't fundamentally disagree with you and I cringe when I hear issues dismissed as "premature optimizations" myself.
- taeric 3y agoI think that is fair. I was approaching this from the perspective of "my old machine was responsive, it is becoming less so." Back on the example of Doom, I understood why my machine at the time couldn't run Quake. It would be frustrating to force everyone to that paradigm.