Viewing page 3 of 6 pages. Previous 1 2 3 4 5 6 Next
Measurement and Analysis Tools
Testbed device listing.
Timed Benchmark Test Details
- NOD32: In-depth virus scan of a folder containing 32 files of varying
size with many RAR and ZIP archives.
- WinRAR: Archive creation with a folder containing 68 files of varying
size (less than 50MB).
- iTunes: Conversion of an MP3 file to AAC.
- TMPGEnc: Encoding an XVID AVI file with VC-1.
- HandBrake: Encoding an XVID AVI file with H.264.
- Photoshop: Image manipulation using a variety of filters, a derivation
of Driver Heaven's Photoshop
Benchmark V3 (test image resized to 4500x3499).
Video Test Suite
1080p | 24fps | ~10Mbps
1080p | 24fps | ~14Mbps
H.264: Space is a 1080p x264 clip encoded from
the Blu-ray version of an animated short film. It features a hapless
robot trying to repair a lamp on a spaceship.
1080p | 24fps | ~22Mbps
H.264: Crash is a 1080p x264 clip encoded from the Blu-ray
version of a science fiction film. It features the aftermath of
a helicopter crash.
720p | 25fps | ~2Mbps
Man Trailer #1 is the first trailer from the feature film
of the same name. It's a YouTube HD video, though technically it
is not quite 720p.
If available, the latest motherboard BIOS is installed prior to testing. Certain
services/features like Indexing, Superfetch, System Restore, and Windows Defender
are disabled to prevent them from causing spikes in CPU/HDD usage. We also make
note if energy saving features like Cool'n'Quiet, SpeedStep or S3 suspend-to-RAM
do not function properly.
Our first test procedure is designed to determine the overall system power consumption
at various states (measured using a Seasonic Power Angel). To stress CPUs we
use either Prime95 (large FFTs setting) or CPUBurn depending on which produces
higher system power consumption. To stress the IGP, we use FurMark, an OpenGL
benchmarking and stability testing utility.
Our second test procedure is to run the system through a video test suite featuring
a variety of high definition clips. During playback, a CPU usage graph is created
by the Windows Task Manger for analysis to determine the average CPU usage.
High CPU usage is indicative of poor video decoding ability. If the video (and/or
audio) skips or freezes, we conclude the GPU (in conjunction with the processor)
is inadequate to decompress the clip properly. Power consumption during playback
of high definition video is also recorded.
Lastly, we run a short series of performance benchmarks a few real-world
applications as well as synthetic tests.
|Help support this site, buy from one of our affiliate retailers!|