Pages: [1]
sbergman27
BAM!ID: 57002
Joined: 2008-08-14
Posts: 2
Credits: 467,961
World-rank: 314,066

2008-08-16 13:34:21

Have a look at :

Host CPU breakdown for ClimatePrediction.net

and sort, descending, by the Average Credit Per CPU Second.

Note all the CPU names with 's' substituted for 'space' in the names. And note how the numbers are totally nonsensical. There is no way that an Athlon XP 2000+ is going to blow away a Q6600. (Yes, I know the comparison is with a single core of the Q6600.) All the results with extraneous 's' characters (and the occasional 'intelx' have completely screwy credit per cpu second values.
[BOINCstats] Willy
 
Forum moderator - Administrator - Developer - Tester - Translator
BAM!ID: 1
Joined: 2006-01-09
Posts: 9419
Credits: 350,105,499
World-rank: 4,520

2008-08-16 14:05:59

These high Average Credit Per CPU Seconds are exported by the project like this, not much I can do about that (as in: nothing). What I will fix is the 's' characters.
Please do not PM, IM or email me for support (they will go unread/ignored). Use the forum for support.
sbergman27
BAM!ID: 57002
Joined: 2008-08-14
Posts: 2
Credits: 467,961
World-rank: 314,066

2008-08-16 16:38:31

These high Average Credit Per CPU Seconds are exported by the project like this, not much I can do about that (as in: nothing). What I will fix is the 's' characters.


Understood. But my impression is that the extraneous 's' characters are associated with the wacky credit per cpu second numbers. The S's act as a flag to indicate the suspect entries. If you remove the 's' characters, that will actually make it harder to distinguish. Can you leave some sort of indicator that the number is questionable? Or better yet, omit those entries, which all seem quite bogus?
BeemerBiker
 
BAM!ID: 53636
Joined: 2008-06-04
Posts: 31
Credits: 55,286,246,634
World-rank: 120

2008-08-16 18:02:07
last modified: 2008-08-16 18:04:39

A high score for a low class cpu can be obtained by using the same hostid for a number of systems. I did this inadvertantly when I cloned a disk drive and used that image to build several systems. About a week later I noticed that one system had a huge daily credit and the others were not reporting anything. I had to detach all the systems to fix the problem. I did not think to check the credits per cpu second but I assume they were unreasonably high also.

I ran an extract of all system haveing 6600 and 2100+ for their cpus
http://swri.info/misc_images/cpu_stats.png
the above came from a snapshot of the boincstat main database and not just the climatepredictor.

Clearly, the 6600 are way at the top. There are a few (3) that are probably misconfigured and the .002104 score is lower then some of the 2100+ devices. Misconfigured could include poor or no interleaving, wrong memory speed, cache not enabled, etc.

I have several dual "MP" athlon systems that I am running mobile XP's in including several plain xp 2100 that I did a bridge mod on to get to work. They do pretty good but will not blow away a nicely configured dual core.

Bios manufactures are responsible for providing the name of the cpu and I have seen the phrase "processor" badly mispelled on various motherboards.
[BOINCstats] Willy
 
Forum moderator - Administrator - Developer - Tester - Translator
BAM!ID: 1
Joined: 2006-01-09
Posts: 9419
Credits: 350,105,499
World-rank: 4,520

2008-08-16 22:53:12

The S's were there because of a bug in the host import script. Instead of the script replacing multiple spaces with a single one, it replaced it with a single 's' (regexp can be a b*tch pain in the *ss... damn, you know what I mean). It's unrelated to the CPCS number.
Please do not PM, IM or email me for support (they will go unread/ignored). Use the forum for support.
[BOINCstats] Willy
 
Forum moderator - Administrator - Developer - Tester - Translator
BAM!ID: 1
Joined: 2006-01-09
Posts: 9419
Credits: 350,105,499
World-rank: 4,520

2008-08-17 10:30:56

The S's are gone.
Please do not PM, IM or email me for support (they will go unread/ignored). Use the forum for support.
Pages: [1]

Index :: BOINCstats Bug Report :: * Host CPU breakdown totally wacky
Reason: