|
3DMark 2000 |
| Setting: |
Score: |
| 150 MHz |
11481 3DMarks |
| 170 MHz |
11645 3DMarks |
As seen in my
earlier review of MSI's K7T266Pro2-Ru, 3DMark2000 doesn't really take advantage
of the bus speed increase. However, Madonion's latest creation, 3DMark2001,
does.
|
3DMark 2001 |
| Setting: |
Score: |
| 150 MHz |
7977 3DMarks |
| 170 MHz |
8022 3DMarks |
I can't really explain these results. Usually 3DMark likes high bus
speeds. Anyway, enough with the synthetics, here are some real games.
|
MDK2 640x480 default |
| Setting: |
Score: |
| 150 MHz |
214.6 FPS |
| 170 MHz |
219.2 FPS |
|
MDK2 1024x768 MAX |
| Setting: |
Score: |
| 150 MHz |
191.4 FPS |
| 170 MHz |
206.7 FPS |
MDK2 is really
starting to show it's age. Unfortunately it's not really useful anymore in terms
of testing. I'll probably only keep it for videocard benchmarking from now on.
Quake III Arena Fastest
setting
|
Quake III Arena: demo001
fastest |
| Setting: |
Score: |
| 150 MHz |
278.7 fps |
| 170 MHz |
284.9 fps |
|
Quake III Arena: nv15demo
fastest |
| Setting: |
Score: |
| 150 MHz |
81.0 fps |
| 170 MHz |
86.4 fps |
Again, at the
fastest setting in Quake III, we're all CPU limited. Still, those are some nice
numbers for a non P4 system.
Quake III Arena HQ
setting
|
Quake III Arena: HQ setting demo001 |
| Setting: |
Score: |
| 150 MHz |
231.4 fps |
| 170 MHz |
245.1 fps |
|
Quake III Arena: HQ
setting nv15demo |
| Setting: |
Score: |
| 150 MHz |
61.8 fps |
| 170 MHz |
68.9 fps |
Quake III Arena MAX
1024x768
|
Quake III Arena:Max
1024x768 demo001 |
| Setting: |
Score: |
| 150 MHz |
175.1 fps |
| 170 MHz |
198.9 fps |
Finally, some
conclusive evidence. Quake III can obviously tell the differences between the
systems. Amazing, at 1024x768 it's almost breaking 200 fps!
RSS Newsletter
