CPU

Message boards : Number crunching : CPU
Message board moderation

To post messages, you must log in.

AuthorMessage
Daniel S. Gandolfo

Send message
Joined: 17 Nov 02
Posts: 56
Credit: 2,430,947
RAC: 0
United Kingdom
Message 791548 - Posted: 2 Aug 2008, 20:35:50 UTC
Last modified: 2 Aug 2008, 20:48:49 UTC

Hello,

I have recently installed the new Ubuntu Distribution on a:

Intel(R) Core(TM)2 Quad CPU Q6600 @ 2.40GHz

which runs:

Linux Ubuntu 2.6.24-19-generic (64bit).

On running the BOINC benchmark now I find:

Sat 02 Aug 2008 21:27:06 BST||Benchmark results:
Sat 02 Aug 2008 21:27:06 BST|| Number of CPUs: 4
Sat 02 Aug 2008 21:27:06 BST|| 1135 floating point MIPS (Whetstone) per CPU
Sat 02 Aug 2008 21:27:06 BST|| 4874 integer MIPS (Dhrystone) per CPU


Previously on a Debian Linux distribution I was seeing
Whetstone = 1800 per CPU
Dhrystone = 9400 per CPU

Any ideas about what could have happened or has the CPU burnt out or something equivalent. Any reason for the loss in performance. Whether the change in distribution is responsible I think it is unlikely.

Nevica
ID: 791548 · Report as offensive
Richard Haselgrove Project Donor
Volunteer tester

Send message
Joined: 4 Jul 99
Posts: 14653
Credit: 200,643,578
RAC: 874
United Kingdom
Message 791561 - Posted: 2 Aug 2008, 20:52:58 UTC

You might like to review this old thread.

Modern Linux distros are - very comendably - concerned about not wasting energy when nothing important is going on.

Unfortunately, the science applications controlled by BOINC (such as SETI) run at the 'nothing important' level. So linux tries to save energy, and invokes the Intel 'Speedstep' or AMD 'CoolNquiet' technology as appropriate. Result: lower CPU speed and reduced crunching.

There are posts with appropriate commands to overcome this in the thread I linked.
ID: 791561 · Report as offensive
Profile Westsail and *Pyxey*
Volunteer tester
Avatar

Send message
Joined: 26 Jul 99
Posts: 338
Credit: 20,544,999
RAC: 0
United States
Message 791565 - Posted: 2 Aug 2008, 20:59:15 UTC

Ubuntu is set to *on demand* power setting by default. This equates to it doesn't think you need to run a low priority task like boinc at more than 50%.
This link shows how to set the scaling to 100%.

Link


Good luck! This would be my best guess.
"The most exciting phrase to hear in science, the one that heralds new discoveries, is not Eureka! (I found it!) but rather, 'hmm... that's funny...'" -- Isaac Asimov
ID: 791565 · Report as offensive
Profile JDWhale
Volunteer tester
Avatar

Send message
Joined: 6 Apr 99
Posts: 921
Credit: 21,935,817
RAC: 3
United States
Message 791591 - Posted: 2 Aug 2008, 21:55:22 UTC - in response to Message 791548.  

Any ideas about what could have happened or has the CPU burnt out or something equivalent. Any reason for the loss in performance. Whether the change in distribution is responsible I think it is unlikely.

Nevica

Looks like you're running 50% speed... the app reports...
Processor Information:
  Model: Intel Core 2 Quad Q6600, 1.20 GHz
  Package: 4 Cores

Good luck,
JDWhale
ID: 791591 · Report as offensive

Message boards : Number crunching : CPU


 
©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.