Message boards :
Number crunching :
Weird benchmark.
Message board moderation
Author | Message |
---|---|
Paul Knibbs Send message Joined: 21 Mar 01 Posts: 5 Credit: 194,839 RAC: 0 |
Why is the computer I just installed BOINC on showing a dhrystone number of over 113,000? I've run the benchmark on it twice now and it comes out the same each time! No way a Sempron 2400+ (or, in fact, any computer currently existing on the face of the planet!) should be able to return those sort of numbers for a single CPU... |
littleBouncer Send message Joined: 28 May 99 Posts: 151 Credit: 666,283 RAC: 0 |
> Why is the computer I just installed BOINC on showing a dhrystone number of > over 113,000? I've run the benchmark on it twice now and it comes out the same > each time! No way a Sempron 2400+ (or, in fact, any computer currently > existing on the face of the planet!) should be able to return those sort of > numbers for a single CPU... > > That's a beauty can U send it to me ?:-) (I mean the CPU) [EDIT] That is a joke, sorry. |
Paul Knibbs Send message Joined: 21 Mar 01 Posts: 5 Credit: 194,839 RAC: 0 |
Well, thanks for that, but I'm kind of worried--this machine is going to be reporting some ludicrously high "claimed credits" and they might all be disallowed, or something! |
SURVEYOR Send message Joined: 19 Oct 02 Posts: 375 Credit: 608,422 RAC: 0 |
better set connect every 0.01 days or will down load all of the wu's ok there is suppost to be 50 file limit. Fred BOINC Alpha, BOINC Beta, LHC Alpha, Einstein Alpha |
Divide Overflow Send message Joined: 3 Apr 99 Posts: 365 Credit: 131,684 RAC: 0 |
Are you using one of the custom optimized linux BOINC clients out there? Some of these optimizations are actually breaking the BOINC benchmark code. The benchmark delibrately asks the computer to run some non-optimized code that custom complied jobs can possibly re-write, giving inflated benchmark results. Crunch a few WU's and see how it does! |
Paul Knibbs Send message Joined: 21 Mar 01 Posts: 5 Credit: 194,839 RAC: 0 |
It's the Linux client downloaded from this very site, and it looks like whatever timing glitch causes the benchmark to go wrong is also affecting the timer for the actual crunching, so they cancel each other out--it's so far crunched 2 units, and it claims they each took around 270 seconds to crunch, even though I know for a fact they must have taken several hours (the machine's been running all night!). Claimed credit is around 25 per unit, which is a little lower than my main crunching machine but not by a massive amount. |
Paul Knibbs Send message Joined: 21 Mar 01 Posts: 5 Credit: 194,839 RAC: 0 |
Update: I just applied some updates to the Red Hat Fedora installation I have, and the problem seems to have reversed itself--I'm now showing just 2000 Dhrystones, whereas a 2400+ should be good for nearer 3500 given some other machines I've seen! |
©2024 University of California
SETI@home and Astropulse are funded by grants from the National Science Foundation, NASA, and donations from SETI@home volunteers. AstroPulse is funded in part by the NSF through grant AST-0307956.