Bad performance with 64 bit Linux?

[the-mk]

Maybe I've found the issue: AMD cool'n'quiet...

took a look at /proc/cpuinfo where it states that the CPU runs at 1000 mhz (even during dnetc)

disabled that feature in bios, now /proc/cpuinfo shows about 2500 mhz

hopefully the MNodes/s increase

[the-mk]

Now it behaves like a 4800+ X2 should do:

[Jul 20 18:13:44 UTC] Automatic processor detection found 2 processors.
[Jul 20 18:13:44 UTC] Loading crunchers with work...
[Jul 20 18:13:44 UTC] Automatic processor type detection found
an AMD K8-11 processor.
[Jul 20 18:13:44 UTC] OGR-P2: using core #4 (GARSP 6.0-asm-rt1-mmx-amd).
[Jul 20 18:13:44 UTC] OGR-P2 #a: Loaded 25/1-6-4-9-18-57 (5.65 Gnodes done)
[Jul 20 18:13:44 UTC] OGR-P2 #b: Loaded 25/1-6-4-9-18-56 (8.28 Gnodes done)
[Jul 20 18:13:44 UTC] OGR-P2: 40 packets remain in buff-in.ogf
[Jul 20 18:13:44 UTC] OGR-P2: 0 packets are in buff-out.ogf
[Jul 20 18:13:44 UTC] 2 crunchers ('a' and 'b') have been started.
[Jul 20 18:19:38 UTC] OGR-P2 #b: Completed 25/1-6-4-9-18-56 (19.47 stats units)
0.00:05:53.75 - [31,616,409 nodes/s]
[Jul 20 18:19:38 UTC] OGR-P2 #b: 25/1-6-4-9-18-56 [19,468,188,016 nodes]
[Jul 20 18:19:38 UTC] OGR-P2 #b: Loaded 25/1-6-4-9-23-51
[Jul 20 18:19:38 UTC] OGR-P2: Summary: 1 packet (19.47 stats units)
0.00:05:53.75 - [31.62 Mnodes/s]
[Jul 20 18:19:38 UTC] OGR-P2: 39 packets remain in buff-in.ogf
[Jul 20 18:19:38 UTC] OGR-P2: 1 packet (19.47 stats units) is in
buff-out.ogf
[Jul 20 18:19:58 UTC] OGR-P2 #a: Completed 25/1-6-4-9-18-57 (17.55 stats units)
0.00:06:14.04 - [31,815,687 nodes/s]
[Jul 20 18:19:58 UTC] OGR-P2 #a: 25/1-6-4-9-18-57 [17,546,561,193 nodes]
[Jul 20 18:19:58 UTC] OGR-P2 #a: Loaded 25/1-6-4-9-51-23
[Jul 20 18:19:58 UTC] OGR-P2: Summary: 2 packets (37.02 stats units)
0.00:06:14.19 - [61.69 Mnodes/s]
[Jul 20 18:19:58 UTC] OGR-P2: 38 packets remain in buff-in.ogf
[Jul 20 18:19:58 UTC] OGR-P2: 2 packets (37.02 stats units) are in
buff-out.ogf

cool'n'quiet

but since the x64-client has a little bit more MNodes/s I'll set up the x64 environment once again...

[IronBits]

Now it behaves like a 4800+ X2 should do:

cool'n'quiet

but since the x64-client has a little bit more MNodes/s I'll set up the x64 environment once again...

Yup! Nothing new there, keep it disabled at all times.

[alpha]

That doesn't explain why the 64-bit client was benchmarking faster than the 32-bit client, but ended up being slower during actual crunching. Or does cool n' quiet only kick in after x seconds of high load?

[the-mk]

IMHO cool'n'quiet leaves the cpu at 1000 MHz, while there is no process using 100% when having a high priority. dnetc has only low priority, so it stays at 1000 MHz... So I think it'll increase MHz if you have a process with higher priority and higher load, but not so with dnetc, since it has low priority.

[IronBits]

Cool and Quiet will try to reduce the processor speed every chance it gets.
When you are crunching, you never want the processor to slow down to save energy ($$$) or to run cooler (Get a bigger HSF).
http://www.amd.com/us-en/Processors/...l?redir=dtqc04

I have it disabled via the BIOS on any computer that I want full performance at all times.
It's a good thing to use when you have a laptop and want to conserve battery life.