|
PCStats Test System Specs: |
processor: |
amd athlon64 3500+ amd athlon64 3700+ |
clock
speed: |
11 x 200 mhz = 2.2 ghz (3500+) 11 x 277 mhz = 3.05 ghz (3500+) 11 x 200 mhz = 2.2 ghz (3700+) 11 x 255 mhz = 2.81 ghz (3700+) 11 x 293 mhz = 3.22 ghz (3700+) |
motherboards: |
dfi lanparty nf4 sli-dr (nf4-sli) |
videocard: |
msi
rx800xt-vtd |
memory: |
2x 512mb mushkin xp4000
redline |
hard
drive: |
120gb wd sata
hdd |
cdrom: |
sony 16x dvd-rom |
powersupply: |
silverstone zeus st65zf 650w
psu |
heatsink: |
prometeia mach ii gt (review) |
Software
Setup |
WindowsXP Build 2600 nVIDIA nForce4 6.39 Catalyst 5.4 |
Benchmarks |
SiSoft Sandra 2005 Super
Pi 1.1 Hexus piFast 4.1 ScienceMark 2.0 Beta PCMark04 3DMark2001 3DMark05 Comanche 4 UT2003 UT2004 Doom 3
| |
We did not
run any office benchmarks because no one would overclock for faster word
processing... Really, trust me, they wouldn't. Also for comparisons sake, we
included the Athlon64 3500+'s results.
SiSoft Sandra 2005 |
Source: Sandra |
|
Sandra is
designed to test the theoretical power of a complete system and individual
components. The numbers taken though are again, purely theoretical and may not
represent real world performance.
Sisoft Sandra 2005 Benchmark
Results |
|
Multimedia Benchmark |
CPU Benchmark |
Memory Benchmark |
Processors |
Integer SSE2: |
Floating-Point
SSE2: |
Dhrystone SSE2: |
Whetstone SSE2: |
Integer SSE2: |
Float SSE2: |
Athlon64 3500+ 2.2 GHz (200/400) |
20997 |
22667 |
9977 |
3615 FPU / 4699 SSE2 |
6014 |
5954 |
Athlon64 3500+ 3.05 GHz (277/498) |
28959 |
31265 |
13849 |
4986 FPU / 6481 SSE2 |
7101 |
7126 |
Athlon64 3700+ 2.2 GHz (200/400) |
21055 |
22647 |
10211 |
3486 FPU / 4513 SSE2 |
6014 |
6008 |
Athlon64 3700+ 2.81 GHz (255/510) Air Cooled |
26736 |
28756 |
12967 |
4426 FPU / 5731 SSE2 |
7353 |
7281 |
Athlon64 3700+ 3.22 GHz (293/500) Prometeia |
30721 |
33042 |
14899 |
5086 FPU / 6585 SSE2 |
8026 |
7942 |
Units: |
it/s |
it/s |
MIPS |
MFLOPS |
MB/s |
MB/s |
The Athlon64 3500+ and 3700+ numbers at stock speeds are
almost identical, which they should be as both processors run at the same 2.2GHz
clock speed. With the Athon64 3700+ clocked at 3.22 GHz, we broke the 8000MB/s
memory barrier!
SuperPI
calculates the number PI to 1 Million digits in this raw number crunching
benchmark. The benchmark is fairly diverse and allows the user to change the
number of digits of PI that can be calculated from 16 Thousand to 32 Million.
The benchmark, which uses 19 iterations in the test, is set at 1 Million digits
then repeated at 8 million digits.
Lower
numbers denote faster calculation times (seconds), and hence, better
performance.
Super Pi |
1 Million Digits: |
Seconds |
Ranking |
Athlon64 3500+ 2.2 GHz (200/400) |
38 |
|
Athlon64 3500+ 3.05 GHz (277/498) |
29 |
|
Athlon64 3700+ 2.2 GHz (200/400) Stock |
37 |
|
Athlon64 3700+ 2.81 GHz (255/510) Air cooled |
29 |
|
Athlon64 3700+ 3.22 GHz (293/500) Prometeia |
25 |
|
8 Million Digits: |
Seconds |
Ranking |
Athlon64 3500+ 2.2 GHz (200/400) |
418 |
|
Athlon64 3500+ 3.05 GHz (277/498) |
312 |
|
Athlon64 3700+ 2.2 GHz (200/400) Stock |
411 |
|
Athlon64 3700+ 2.81 GHz (255/510) Air cooled |
325 |
|
Athlon64 3700+ 3.22 GHz (293/500) Prometeia |
287 |
|
Super Pi loves memory bandwidth as well as L2 cache size
and that's why the Athlon64 3700+ clocked at 2.81 GHz performs almost as fast as
the 3500+ @ 3.05 GHz. Very nice numbers here. Completing the eight million digit
test in under five minutes is very fast indeed!
Hexus piFast |
Source: Hexus |
|
Pifast is a
small program that computes Pi to a set amount of decimal places and also
displays how long it takes. This then gives us a basis for charting the results,
giving a performance indicator for new and old technology at a
glance.
Lower results are better.
Hexus piFast |
Processors: |
Seconds |
Ranking |
Athlon64 3500+ 2.2 GHz (200/400) |
54.09 |
|
Athlon64 3500+ 3.05 GHz (277/498) |
40.38 |
|
Athlon64 3700+ 2.2 GHz (200/400) Stock |
52.23 |
|
Athlon64 3700+ 2.81 GHz (255/510) Air Cooled |
42.08 |
|
Athlon64 3700+ 3.22 GHz (293/500) Prometeia |
37.02 |
|
piFast is also very memory bandwidth dependant and it's
easy to see which processor is fastest here!