When it comes down to it, it doesn't really matter. If you feel cheated because someone with a faster machine is pushing more units out and racking up a higher RAC you should upgrade. AP task are 2 credits, CPU tasks are 1 credit, GPU tasks are. Or how about simply breaking apart CPU, GPU, and AP tasks. It doesn't need to be as complicated as it is, because after all this isn't a competition. This would also account for the time it has taken, newer hardware, and how many work units you have processed. Once it has been performed once it will do nothing but climb along with the hardware getting faster. Of course this would also require a lot better system benchmark that it accurate within limits.Įvery quarter the project tasks all the averages and averages those to reach a "milestone" credit average in which you can be granted no less than that per workunit. 1 credit per work unit X the multiplier of predetermined speed your computer is, then you take the fastest machine and the wingman average out that number multiply it by 1 and that's the credits. Statistical multipliers is the answer! lol. Just don't force your believes onto others. It's all your own choice what you do with BOINC. In the end it'll be projects with outdated back-end code with users running outdated BOINC versions.ĭo we care though? I don't. Of course, then you have to convince the user to upgrade to that BOINC version. So then it comes down to the client, which will have to start treating same resource share projects as same RAC projects, whereas projects that overpay -and the client knows about this- will eventually receive less and less CPU/GPU attention. However, there are plenty of projects where the admin thinks he knows better and where they disable the credit portion of the back-end. What you're forgetting, and what everyone seems to forget, is that BOINC is more than just The BOINC back-end version that the developers may be able to run on this project is not necessarily the version that other projects will run, ever.Īnd as such, whatever new credit scheme is introduced and implemented in the BOINC back-end, will then first have to be used by all BOINC projects before it can be measured as a fail or success. I'm not saying its perfect to run wu's completed/hours processed, but it'd be a lot less corrupted that the system is now.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |