You are viewing a single comment's thread from:
RE: Time and Work Based Model for GridCoin Reward Mechanism
One of the issues with this is that performance on a given CPU project is not just determined by CPU performance. The primary example of this VGTU which has a strong dependence on memory bandwidth.
i.e. you would need to control for memory type, frequency, and number of channels (single dual quad).
Contrary, proposed solution would address this problem. It's seems I've cut some text off before publishing and it might not be obvious. Graphic card or a processor cannot run by itself. But they are crucial factors. This is why I have focused on them in the post. The point is to run the same or very close configuration in each of the respective class of the projects. Chosen configuration performance is a benchmark for credit normalization. Basic requirement is that GPU or CPU is not starved of other resources. Topic needs further research.
Makes sense. My point however is to be careful and don't assume that any of the task metrics are consistent between projects. Or that the project performance is dependent on the piece of hardware you think it is. Use a large variety of reference machines.
I've been working on making a magnitude/rac calculator and its become apparent that some of the projects don't even report cpu/wall time the same way as other projects.