|
|
Benchmark testing is essential in evaluating performance gains or losses from overclocking. Two types of benchmarking techniques are available: synthetic and real world. Synthetic benchmarks use a series of performance-testing algorithms and enable you to compare your system's results with results generated from other systems, across all platforms. Synthetic benchmark results for a single system are not useful; they must be compared to results obtained on other systems. Real-world benchmarks test actual performance for common operating scenarios, in real time. Results are often measured in frames per second or operations per second.
Benchmark results can provide a foundation for determining the best combination of multiplier and bus overclocking techniques. Increasing system bus rates, while decreasing or maintaining processor multiplier settings, may produce better performance than raising multiplier values alone. A thorough benchmarking process can help you analyze the various impacts on performance and stability introduced by overclocking.
It is important to establish baseline performance numbers on your system before you do any overclocking, so that you can make before-and-after comparisons. Overclocking does not always improve computing results; sometimes it brings negligible gains or even declines in performance. Before-and-after comparisons will help you determine whether or not your overclocking efforts have succeeded and if further adjustments are necessary.
System stability is often affected by overclocking, so it is valuable to determine what impact your efforts have had on stability without having to experience failures (that is, system hang-ups and crashes) in your real-world applications. Benchmarking apps involve strenuous system tests that exceed the level of CPU power and resources required by typical applications in everyday use. During such tests, a system can be pushed to its limits. If the system fails, it is probably either overclocked beyond its capabilities or in need of additional tweaks. Increasing CPU voltage, improving the cooling, or reducing bus speed while increasing the CPU multiplier may yield better results.
A few simple steps will ensure that your system is properly configured for benchmarking.
Your desktop display resolution should always be set to the same value for each pass or test run of a given application. A resolution of 1024 x 768 pixels with 16-bit color is recommended for consistency and comparable results.
All hard disks in your system should be thoroughly defragmented before testing to ensure maximum bandwidth, low access latencies, and a consistent data flow among each of the system components and the drive array.
Finally, all components (video, chipset, etc.) should be installed using the latest software drivers from each hardware manufacturer.
|
|