I have a AMD 3500+ 64bit, and i´m running windows xp x64.

But my performance is poor, only 2,1s/TS
or if i do a benchmark:
2118 double precision MIPS /CPU
3805 Integer MIPS /CPU

is there anyway to speed up my comp, or is there a x64 bit verson comming?
What are you other guys bench?
Running BONIC, should i run classic, ifso were do i find it?

---

A 2.2 GHz AMD64 will benchmark pretty much as you have it there. BOINC CPU benchmarks do not in any way equate to CPDN performancd. However, your s/TS in CPDN is slower than I would think. I would think it should be down in the 1.8-1.9 s/TS range.

You\'re not running the visualization/screensaver much are you?

Also, AMD64 likes low-latency dual channel memory. If your memory is high latency, and/or you are not running your memory dual channel, this might explain the relatively slow s/TS.

From all indications, a 64 bit compiled version is not coming anytime soon.

You\'re not running the visualization/screensaver much are you?

Also, AMD64 likes low-latency dual channel memory. If your memory is high latency, and/or you are not running your memory dual channel, this might explain the relatively slow s/TS.

From all indications, a 64 bit compiled version is not coming anytime soon.

Nope.. turning of the monitor instead, will running it as a screensaver increse performance?

Running my memmory in dualchannel, have 1024Mb cas 2,5
not so high right?

---

Nope.. turning of the monitor instead, will running it as a screensaver increse performance?

Definitely not.

Running my memmory in dualchannel, have 1024Mb cas 2,5
not so high right?

Sounds pretty good. I\'m not sure why your s/TS are that high.

If you run Everest diagnostic software, what are your memory read, write, and latency scores?

If you run Everest diagnostic software, what are your memory read, write, and latency scores?

Read: 5690MB/s
Write:1608MB/s
Latency: 52,1ns

Is this normal?

---

Read: 5690MB/s
Write:1608MB/s
Latency: 52,1ns

Is this normal?

Not bad except the write seems slow. In Everest, when you go to Computer, Overclock, Chipset Properties, what does it say for motherboard chipset, memory timings and command rate?

what does it say for motherboard chipset, memory timings and command rate?

Timings: 2,5-3-3-5
Comandrate 2T

---

what does it say for motherboard chipset, memory timings and command rate?

Timings: 2,5-3-3-5
Comandrate 2T

command rate 2T = bad.................

try running at 1T this setting is adjustable in your BIOS memory settings

---

try running at 1T this setting is adjustable in your BIOS memory settings

Thanks.. that did it for the benchmarks:

Read: 5687MB/s
Write: 2277MB/s
Latency: 49,9ns

but the problem with the 2,1s/TS remains, havent noticed any difference...

Made an overclock on the cpu by 11% and tweaked the ram as much as possible, but still no difference in speed, so it seams that the speed have locked itself or something. Or might it be a bug in windows XP x64?
any more advice?

---

but the problem with the 2,1s/TS remains, havent noticed any difference...

Made an overclock on the cpu by 11% and tweaked the ram as much as possible, but still no difference in speed, so it seams that the speed have locked itself or something. Or might it be a bug in windows XP x64?
any more advice?

The s/TS calculation is cumulative, depending on how far you are into the model, it may take awhile for this number to drop.

I am having severe problems keeping my machine afloat for more than a few hours at a time while running this program on x64. Please see my numerous posts here (and on the bbc.cpdn) for the sorry tale, i can\'t bear going over it all again...

Basically, the machine turns itself off after writing to disk. There are no error messages, and the machine can be rebooted without any \'windows wasn\'t shut down properly\' procedures. I have updated directx, all drivers are current. The same five \'dataout\' files are always the most recently modified. I have variously disabled network cards, display drivers, sound card, firewire etc. but to no avail. The problem occurs even when cpdn is the only program installed on a fresh, fully updated installation of x64. The machine runs indefinitely when not running cpdn.

The machine should be able to cope easily: it has run a number of Prime95 torture tests (two simultaneousl tests, one per CPU) for 6-24 hours reliably and without errors. CPU temps are below 50 flat out, MB below 35. Pagefile is locked at 7Gb, lashings of RAM, BOINC runs cpdn in its own partition, which is defragged regularly. Speeds are slow by the figures discussed in this thread: 2.38 and 2.35 s/TS. Does this indicate a problem?

I have tried running at least 7 hadcm3 models on both the bbc installation and BOINC 5.4.9 and the problems are the same on all counts. How can i tell if this is a file corruption, software conflict or program bug? Is there anywhere to send files?

---