Next, we have a slick little Folding@Home benchmark CD created by notfred, one of the members of Team TR, our excellent Folding team. For the unfamiliar, Folding@Home is a distributed computing project created by folks at Stanford University that investigates how proteins work in the human body, in an attempt to better understand diseases like Parkinson's, Alzheimer's, and cystic fibrosis. It's a great way to use your PC's spare CPU cycles to help advance medical research. I'd encourage you to visit our distributed computing forum and consider joining our team if you haven't already joined one.
The Folding@Home project uses a number of highly optimized routines to process different types of work units from Stanford's research projects. The Gromacs core, for instance, uses SSE on Intel processors, 3DNow! on AMD processors, and Altivec on PowerPCs. Overall, Folding@Home should be a great example of real-world scientific computing.
notfred's Folding Benchmark CD tests the most common work unit types and estimates the number of points per day that a CPU could earn for a Folding team member. The CD itself is a bootable ISO. The CD boots into Linux, detects the system's processors and Ethernet adapters, picks up an IP address, and downloads the latest versions of the Folding execution cores from Stanford. It then processes a sample work unit of each type.
On a system with two CPU cores, for instance, the CD spins off a Tinker WU on core 1 and an Amber WU on core 2. When either of those WUs are finished, the benchmark moves on to additional WU types, always keeping both cores occupied with some sort of calculation. Should the benchmark run out of new WUs to test, it simply processes another WU in order to prevent any of the cores from going idle as the others finish. Once all four of the WU types have been tested, the benchmark averages the points per day among them. That points-per-day average is then multiplied by the number of cores on the CPU in order to estimate the total number of points per day that CPU might achieve.
This may be a somewhat quirky method of estimating overall performance, but my sense is that it generally ought to work. We've discussed some potential reservations about how it works here, for those who are interested. I have included results for each of the individual WU types below, so you can see how the different CPUs perform on each.
However, the individual results for each unit type tend to get a little wonky because the CPUs with Hyper-Threading are running multiple threads on each core. To get a clear sense of performance for all CPUs, you'll want to focus on the final graph showing total projected points per day.
This is our final benchmark test (phew!), and it's another case where the Athlon II X4 635's four true cores give it the win. Even so, the Core i3-530 delivers more points per day than the Core 2 Quad Q6600, showing that two of today's cores are sometimes superior to four of the prior generation's.
|AMD posts Fury X top plate schematics, customization guide||24|
|Half-Life 2: Episode Two and more new games arrive on Shield||2|
|Double the fans, double the fun with Gigabyte's new mini-GTX 960s||8|
|New Unreal Engine 4 demo videos continue to amaze||11|
|Acer unleashes a 34" curved FreeSync monitor||12|
|F1 2015 revs up with new teaser trailer||10|
|The TR Podcast 179: Radeon R9 Fury X tested & dissected||10|
|Fractal Design's Define S case reviewed||19|
|Microsoft adds $1,299 Core i7 version to Surface Pro 3 lineup||51|