Posts by mario

1) Message boards : Documentation : Cobblestone / BOINC credit / CPU time / GFLOPs equivalency documentation discrepancy (Message 86030) Posted 28 Apr 2018 by mario Post: Also sad to discover that all my crunching devices are performing half of what, at least in theory, they should be performing. But that´s a different story. Since the ACTUAL award of credits is down to the individual projects, and NO PROJECT actually obeys the theoretical figures you have fallen foul of theory vs reality. One should NEVER use credits awarded to compare computer performance between projects. What you now have to do is look and see how your computer compares with other similar computers that are running the same pattern of work as you are on each of the projects you are taking part in, I know doing this is a long winded task, and will take a lot of time to find comparable computers to your own that are running the same set of projects with the same work shares etc. I see. I will keep this in mind. Thanks for your answers Rob.
2) Message boards : Documentation : Cobblestone / BOINC credit / CPU time / GFLOPs equivalency documentation discrepancy (Message 86023) Posted 28 Apr 2018 by mario Post: Sorry, I could have answered this from memory yesterday, but it's proved hard to locate the documentary evidence that you have the right to request. Your second statement is the one officially recognised by BOINC: 1 BOINC credit equals 1/200 day CPU time @ 1 GFLOPs/second There are two complementary calculations: "How many credits should I get for a day's processing on a 1 GFLOP device?" Answer = 200 "How many Fpop-days did I compute in order to earn 1 BOINC credit?" Answer = 1/200 Great, thanks for the detailed explanation. I am glad this detail is explicitly documented here in case anyone else runs into it. Also sad to discover that all my crunching devices are performing half of what, at least in theory, they should be performing. But that´s a different story. Thanks everybody.
3) Message boards : Documentation : Cobblestone / BOINC credit / CPU time / GFLOPs equivalency documentation discrepancy (Message 85970) Posted 23 Apr 2018 by mario Post: Hello Rob. I perfectly understand what you are saying, but it is not what I am talking about. I am not refering about the different credit definitions of different projects. Please follow the links I posted on my first message. I am talking about the definition of Cobblestone. There can be just one definition for it. It would be great if anybody involved in the design, development and/or maintenance of the BOINC code base can clarify this. Do anyone of them hang out in here at all? And whatever the right definition is, the wrong online documentation should be fixed. A very graphic example is that the English Wikipedia entry for "BOINC Credit System" gives one definition, and the same entry in the Spanish version gives the other one.
4) Message boards : Documentation : Cobblestone / BOINC credit / CPU time / GFLOPs equivalency documentation discrepancy (Message 85967) Posted 23 Apr 2018 by mario Post: Hi Rob, thanks for your comments. I understand the fact that different BOINC projects may have different credit/GFLOP assignement values, it is actually one of the first things I noticed when trying to understand BOINC credit. For example, that 7 World Community Grid credits equal to 1 BOINC credit (1 Cobblestone). I also undestand the difficulty to properly compare GFLOPS on different CPUs/GPUs/APUs architectures, models, generatios, and that many other variables can affect it. What I am trying to point out is that there is documentation online that define the exact same thing, the Cobblestone (BOINC credit), in 2 different ways: 1) As 1/100 day CPU time @ 1 GFLOPs/second (I really think this is the right one) 2) As 1/200 day CPU time @ 1 GFLOPs/second If I am wrong, the documentation should be corrected in the first set of 3 links I mentioned in my original post. But, if I am right, the documentation in the official BOINC Wiki and on the English Wikipedia article (the Spanish Wikipedia article use the other definition), are the ones that would be wrong. And something should be done about it (please refer to the second set of 3 links I mentioned in my original post). Using an analogy: it is like defining the mile as 1,609.34 meters and also as 3,218.69 meters. I am just trying to save other people the confusion about a subject that is not trivial to understand by itself. There should be one single definition for the Cobblestone.
5) Message boards : Documentation : Cobblestone / BOINC credit / CPU time / GFLOPs equivalency documentation discrepancy (Message 85963) Posted 22 Apr 2018 by mario Post: I have been running BOINC for almost 10 years now, and I had never bother to figure out exactly what a BOINC credit meant, I just knew more is better :) I ran over this when doing some research that would help me to take an informed decision regarding my future computer hardware upgrade. The goal was to try to identify the CPUs and GPUs with the best GFLOPS/price and GPLOPS/Watt relations, withing a certain budget, and having BOINC in mind. I found 2 very different definitions for the BOINC credit: - Sources that state that 1 BOINC credit equals 1/100 day CPU time @ 1 GFLOPs/second https://es.wikipedia.org/wiki/Sistema_de_cr%C3%A9ditos_de_BOINC http://www.gridrepublic.org/joomla/components/com_mambowiki/index.php/More_about_Credits,_GFlops,_G-hours,_and_CPU_hours https://www.worldcommunitygrid.org/help/viewTopic.do?shortName=points#177 - Sources that state that 1 BOINC credit equals 1/200 day CPU time @ 1 GFLOPs/second https://boinc.berkeley.edu/trac/wiki/CreditGeneralized http://boinc.berkeley.edu/wiki/Computation_credit https://en.wikipedia.org/wiki/BOINC_Credit_System Surprisingly, in some cases, sources with different definitions do refer to each other. After much head scratching, and doing some calculations with the credits that my crunching devices got for the last month, I concluded that the first one is the right definition. Is it? Can the we finally and correclty state that: 1 BOINC credit = 1 Cobblestone = 1/100 day of CPU time @ 1 GFLOPs/second = 864 GFLOPs (billion instructions)

Copyright © 2024 University of California.
Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation.