Mephistopheles :
A friend of mine from work is building a small workstation for himself and has asked me about components. He doesn't really have a lot of money, but I recommended "the basics":
Cooler Master Centurion 5
Intel Core 2 Quad 2.4Ghz
Asus P5K Deluxe
Mega Pack OCZ 4GB DDR2-800 Low Latency
Thermalright Ultra-120 Extreme
SATA DVD Recorder Samsung (Black)
Seagate Barracuda 7200.10 320GB
Corsair VX450W PSU
XFX 8400GS Video Card (basics only)
Noctua NF-S12 120mm Fan
Because this is a workstation, I selected better-than-usual cooling for him. We're also from Brazil, which means our room temperature can get to the 30 degrees Celsius... So an aftermarket heatsink is a good idea.
What do you think? Any comments would be appreciated!!
The hardware sounds pretty good, although I'd make a few suggestions about its deployment:
1. Make sure you have a 64-bit OS or you will not see all 4 GB of your RAM. Plus, if you have a 64-bit version of your software or can compile it, you will likely see a performance boost over the 32-bit version.
2. You will want to have an uninterruptable power supply (UPS) if you run calculations for more than a day or so at a time. Trust me on this one, I lost a run I was doing for 40 days due to the power going out for five minutes- I was extremely pissed. A UPS would have kept the unit going or at least let me suspend it, saving my run.
3. Are you sure 4 GB RAM is enough? I don't know your workload, but almost every number-crunching task I've ever done has taken as much RAM as I could throw at the machine, which was 4-8 GB in a dual-core machine. Your proposed machine can take 8 GB RAM maximum.
4. DO NOT OVERCLOCK. You will likely cause your computer to make calculation mistakes if you do. If you want more speed, refund the Q6600 and buy a Q6700 or a QX6850 instead.. Also, overclocking will cause the computer to throw off a lot more heat than it does at stock. You have a production machine here- overclocking a production machine is probably #3 on the list of things not to do do, behind using untested OS/program updates and using the computer to surf porn and catching viruses.
5. You should consider using a redundant HDD array if you have calculations that run for a significant amount of time. Then when an HDD dies, it won't take the machine and your last calculation run down with it and force you to re-run the calculation.
6. Backups...never bad to make sure that important work gets backed up from the machine often. I might sound paranoid, but I've seen too many people lose things off computers when HDDs die, and they do die, often at the most inopportune time. It's no big deal to slap a new HDD in the computer when it dies when you maybe lost a few hours or a day's worth of work, but it's a big pain to re-run weeks or months of work that died along with the drive.
There, that should help you out some. I have built and run several number-crunching machines and am more than happy to help with any issues you might have or questions you want to ask.