• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

memory timings for DC projects

Khyron320

Senior member
My HyperX3500 is almost at my doorstep what do the DC projects like more crazy mad MHZ bump ups or extremely low latency?

Im more interested in how Folding@home is effected then other DC projects.

The rig:
A7N8X REV 1.04 (so over 185mhz fsb will really not be possible)
XP1700 Rev B 310 currently at 1.8ghz with a 144mhz fsb casl2.5 i havent touched the timings on the old ram it got unstable with every changed setting
 
The best combo will be high FSB and low latency 🙂

That RAM should be able to do pretty darn low latency settings, as well as high speeds, so I guess the best thing to do would be to test low latency and higher FSB and see which is best


Garry
 
That memory is going to be able to go way faster than your board will go. Set the timings to 2-2-2-5 and run the highest fsb possible.
 
😎

Playing around with memory timings made a noticable boost in my SB production. Alas, I never ran F@H, so I could not answer your preferred DC project 🙁.

The 1.04 can't hit 200FSB? I thought they all could 😕
You memory will surely handle that slow speed 😛. When you try it out, just lower your multipler to something like 7 and try 200FSB. If it hits it, gradually increase your multipler until it won't boot at 200FSB.
 
I have modest FSB OC, but the ram timings are maxed out and Im getting great performance with Athlons in TSC/D2Ol. You definitely need to test for max stability on anything that runs at 100 percent utilization on the CPU, so Im guessing ram timings will be your best friend over max FSB.
 
Originally posted by: amcdonald
That memory is going to be able to go way faster than your board will go. Set the timings to 2-2-2-5 and run the highest fsb possible.


This is what I was running my hyperx at.
 
You might want to do some preliminary stability testing with memtest86 (just a full loop or two to see if your memory can handle the speed and timings), and then a few hours of Prime95; it will save you the loss in score of having several WUs thrown out due to corrupted results as you experiment and find the limits of your system.
 
Back
Top