Page 4 - Benchmark: AIDA64 FPU
About AIDA64 Extreme Edition
AIDA64 Extreme Edition is a streamlined Windows diagnostic and benchmarking software for home users. AIDA64 Extreme Edition provides a wide range of features to assist in overclocking, hardware error diagnosis, stress testing, and sensor monitoring. It has unique capabilities to assess the performance of the processor, system memory, and disk drives. AIDA64 is compatible with all current 32-bit and 64-bit Microsoft Windows operating systems, including Windows 7 and Windows Server 2008 R2.
AIDA64 implements a set of 64-bit benchmarks to measure how fast the computer performs various data processing tasks and mathematical calculations. Memory and cache benchmarks are available to analyze system RAM bandwidth and latency. Processor benchmarks utilize MMX, 3DNow! and SSE instructions, and scale up to 32 processor cores. For legacy processors all benchmarks are available in 32-bit version as well. AIDA64 Disk Benchmark determines the data transfer speed of hard disk drives, solid-state drives, optical drives, and flash memory based devices.
From: Developer's Page
Usually, AIDA64's FPU benchmarks are the least exciting of all when writing a RAM review. This is because the way results are obtained is usually highly dependent on the tested processor; so much to an extent that the outcome is practically irrelevant to the speed or latencies of the installed memory modules. As you can see in our graphs above, all the results are within a fraction of a percent of each other. In the case of Kingston's HyperX Beast KHX21C11T3K2/16X 2x8GB dual channel kit, it tied for first place a couple of times, while keeping within a hair of the competition the rest of the time.
1. Introduction, Packaging, Specifications
2. A Closer Look, Installation, Test System
3. Benchmark: AIDA64 CPU
4. Benchmark: AIDA64 FPU
5. Benchmark: AIDA64 Memory
6. Benchmark: PCMark 7
7. Benchmark: 3DMark 11
8. Benchmark: PassMark PerformanceTest 7.0
9. Benchmark: SuperPI 1M, Cinebench R11.5
10. Overclocking and Conclusion