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

What makes a fast DF box?

I'd like to know also.

I changed the CAS latency of my P3 933@1000 box tonight from 3 to 2 and my structures/second went from 1.8 to 2.0.
 
There is a Graphic User Interface (DFGUI v1.8) that you can d/l here that I have been using with the DF Client.

It does a nice job of letting you see what the DF client is doing and also shows benchmarks of projected production rates.

I suggest using DFGUI and experimenting (ie: tweak, run for a bit and record the production projections. Then, tweak again.... rinse, lather, repeat... )

You can blaze a train for us all
 
Yeah DFGUI will work for tweaking RAM settings and such and finding the best configuration. However, if we knew what sorts of computation DF did they we would know which processors would theoretically do better at it. If it requires fast FSB and low latecy then you could go with and overclocked machine or wait for the Hammer with built in memory controller. Or if it is very FPU intensive you could pick a processor that excells in that area.

Most of us I'm sure don't pick our machines just based on DC performance but for those wanting to build crack racks or dedicated crunchers it would be very helpful. This info has also been used in the past for CPU exchanges ie. you run this project for me and I'll run yours for you because our machines are better suited for those projects.
 
has also been used in the past for CPU exchanges

I always thought that was a cool idea.

Anybody try contacting the DF peeps and see if they have input?

(I'll stick a note in their forums and see if we get a nibble)
 
Depends on what you're running. I run Folding@home, and from what I've read at the various sites, it's the FPU that's most important. Here's a page that details various processors and folding times. Note that AMD processors are the KING of folding@home, but I cannot comment on other programs.

http://home.attbi.com/~wxdude1/emsite/foldspeed.html

From what I gather in the various conversations, it's purely CPU power that matters. FSB doesn't seem to enter into it. Nor does memory speed. CPU pure and simple. 🙂

 
Quoted from Compatibility Notes for the Distirbuted Folding Project software package

Compaq Alpha
------------
This version is built for a Compaq Alpha 21264 CPU (also called EV6) and
uses instructions tuned for the 21264 command set. However, earlier Alpha
CPUs should run the code without problems to the best of our knowledge. It
is worth noting that this platform has been found to be by far the fastest
at executing the Foldtraj code and so is recommended. This version has NOT
been thoroughly tested so please let us know if you experience any problems.
It was built on version 4.0F (1229) of the Tru64 operating system.
 
Back
Top