![]() |
|
In the Forums... |
Posted: June 5th, 2001 Written by: Tuan "Solace" Nguyen Benchmark System Two AMD Athlon MP 1.2GHz processors Two AMD Athlon “Thunderbird” 1.2GHz (266MHz FSB) processor Tyan Thunder K7 Motherboard (AMD 760MP chipset) Asus A7V133 Motherboard (VIA KT133A chipset) Corsair 512MB PC2100 Registered DDR SDRAM Corsair 512MB PC133 SDRAM Asus V8200 Deluxe (NVIDIA GeForce 3) with Detonator 12.40 IBM Deskstar 75GXP 30GB UltraATA/100 Hard drive Intel Management S 100Mbps NIC (disabled dual 3Com Ethernet on Thunder K7) Hitachi GD-7000 12X DVD ROM Windows 2000 Professional with SP2 (service pack 2) SiSoft Sandra 2001 Pro: CPU and Memory benchmark BAPCo: SysMark 2000 and Webmark2001 Ziff Davis Dual Processor Inspection: Micro Station SE Adobe Photoshop 4.0 Microsoft Visual C++ 6.0 Inspection Overall Adobe Photoshop: PSBench 6.0.1 CSA Research: Benchmark Studio 2001 MadOnion.com: 3DMark2001 (full benchmark with Nature and DX8 tests) Id Software: Quake 3 Arena 1.25y with r_smp console command enabled - 640x480x32bit Benchmarks can be divided into two kinds, component and system. Component benchmarks measure the performance of specific parts of a computer system, such as a microprocessor or hard disk, while system benchmarks typically measure the performance of the entire computer system. In either case, the performance you see in day-to-day use will almost certainly vary from benchmark performance, for a number of reasons. First, individual components must usually be tested in a complete computer system, and it is not always possible to eliminate the considerable effects that differences in a system design and configuration will have on a benchmark result. For instance, system vendors sell systems with a wide variety of disk capabilities and speeds, system memory, system bus features and video and graphics capabilities, all of which influence how the system components (such as the processor) and the computer system perform in actual use and can dramatically affect benchmark results. Also, you may not actually purchase the exact components we use in your benchmark system. This is just a reference you can base your purchase decisions on. Also, differences in software, including operating systems and compilers, will affect component and system performance. Finally, benchmark tests are typically written to be exemplary of only a certain type of computer application, which may or may not be similar to your applications. Benchmarks are, at most, only one kind of information that you may use during the purchasing process. To get a true picture of the performance of a component or system you are considering purchasing, you must consult other sources of information (such as performance information on the exact system you are considering purchasing). You may also want to try actually sitting down and using the system if possible. There’s no better way to get a feel of a system than actually using it. Let’s take a look at how the Athlon MPs and 760MP chipset perform. |
||
|
---|