This scenario will likely apply to many of us watching video on our PCs without hardware-accelerated video. It’s a bit more interesting to look at because, with this scenario, we will be able to see power consumption when the processor is fully loaded.
Interestingly, DivX uses fewer resources for playback than WMV. A multi-thread codec is able to spread the task more evenly between available cores. In effect, this means having more cores (in lower p-states) leads to more savings than having fewer cores (in intermediary p-states). Compare the DivX and WMV graphs. With WMV, all processors are unable to use lower p-states (and thus unable to save power) compared to DivX.
That doesn’t mean DivX is not resource-intensive. Just look at the Athlon X2 7750 and Phenom II X3 710. These processor lack the performance to play our DivX test video clip while in their lowest p-states, forcing them to use the higher/highest p-state. You can keep this from happening by customizing the multiplier used by the lower/lowest p-states as demonstrated in Part 1.
- Test System And Benchmarks
- Benchmark Results: 3DMark 2001
- Benchmark Results: 3DMark Vantage
- Benchmark Results: SuperPi 1M And 8M
- Benchmark Results: WinRAR
- Benchmark Results: Cinebench R10
- Benchmark Results: POVRay 3.6
- Benchmark Results: Photoshop CS4
- Benchmark Results: Video Encoding
- Benchmark Results: 1080p WMV With VirtualDub And DivX
- Benchmark Results: 1080p AVI With VirtualDub And XviD
- Benchmark Results: Audio Encoding
- Benchmark Results: Video Playback
- Benchmark Results: DivX And WMV, No Hardware Acceleration
- Update: The Athlon II X4 620
- Performance And Power Management, The Best Of Both Worlds