credits and workunits: a fair system needed for Boinc |
![]() |
| log in |
Message boards : Number crunching : credits and workunits: a fair system needed for Boinc
Previous · 1 · 2 · 3
| Author | Message |
|---|---|
|
Well said, Mark. For myself, I care little or nothing for the 'credits'...they will continue to be just meaningless numbers, when there is no relation to anything much at all. I just do S@H and thats it; the place where the fairly large number of 'spare cycles' I have, is used. Merely contributing to the 'crunching' is sufficient for me.....when you have PCs such as I have available, one has very little to prove! "I am a Vulcan, I have no ego to bruise" (Captain Spock, of the USS Enterprise, to Admiral James T Kirk, in Star Trek 2). | |
| ID: 1132260 · | |
|
I've been a SETI@home participant since '99 but I did stray away for a while while I participated in a non-BOINC-based project. I recently directed my computers back to the SETI because of an issue I had with the points system with the other project which I felt was not beneficial to the science. | |
| ID: 1132262 · | |
|
| |
| ID: 1132269 · | |
To put it another way, why should my credits depend on how much work my wingman did? ... because you both did exactly the same amount of work. Sure, you've got a fancy GPU and spent five minutes doing it, while his six year old Celeron took a week, but the same amount of math was done. That's equal pay for equal work. The difficulty lies in differences between processors, differences between the instruction mix in the benchmarks and the science applications, differences in cache sizes and memory speeds. All of the systems we have are "fair" if by fair you mean "equitable." The credits may not accurately reflect the amount of work, but everyone has the same chance of being overpaid or underpaid, and everyone gets the same. Benchmarking was an inexact science in the 1950's, when computers were very simple, and you could calculate exactly how many clock cycles it'd take to get through a loop -- no cache faults, no wait states. It's even harder to accurately measure work now. | |
| ID: 1132272 · | |
The difficulty lies in differences between processors, differences between the instruction mix in the benchmarks and the science applications, differences in cache sizes and memory speeds. So should the benchmarks be required to be optimized if you run an optimized application? ____________ | |
| ID: 1132295 · | |
The difficulty lies in differences between processors, differences between the instruction mix in the benchmarks and the science applications, differences in cache sizes and memory speeds. That is actually a great question, and one that was discussed at great length some time ago. The consensus was "no" -- if you want to run an optimized app., you should get some advantage to go with the hassles. I haven't followed the latest, but the previous credit system attempted to approximate benchmark * time by counting passes through loops and estimating the work done each time. The problem is the need for some conversion factor that was to be determined experimentally to get you to the proper credit. If you're a project scientist, that scaling factor has nothing to do with science at all. So, too many projects have just taken a swipe at it, and if they overpaid, no big deal. They can double the amount of "nothings" given per work unit and it's all the same to them. If anything, it is in a projects' best interest to overpay. Last I knew, most projects (including SETI) overpaid by about 3:1. | |
| ID: 1132323 · | |
|
As far as I'm concerned, we could do away with numbers entirely for scoring SETI@Home. | |
| ID: 1132426 · | |
|
What he said. | |
| ID: 1132515 · | |
|
I think somebody forgot their medicine. However I do agree. | |
| ID: 1132530 · | |
Message boards : Number crunching : credits and workunits: a fair system needed for Boinc
| Copyright © 2013 University of California |