Originally Posted by assassin
Glad to see that drivers are improving for AMD. Was quite disappointed with power consumption though.
Overall I like what I am seeing with the new Trinity platform.
Same here. Very disappointed with the power profile, but I have to say that it is a 100W TDP part. So, I should probably cut some slack. Not sure what would happen if we go to one of the 65W TDP parts. Also, hoping that the future driver releases don't break what is working in the current one.
Originally Posted by Ruiner
The 65W A8 seems to be the HTPC choice over the A10K Anand tested. That article shows 84% gpu utilization with madVR and LAV copy-back for 1080i60p VC1...on the A10. I wonder if the A8 can pull that off without hitting 100%. Is that type of content common enough to be an issue?
Please note that DXVA2CB + madVR for 1080i60 / 1080p60 is NOT working properly. Note the emboldened text beneath the table. We have software decode + madVR working without problems. For Ivy Bridge, even software decode + madVR was an issue. However, in the QS or DXVA2CB / madVR case, I have to say that the number of dropped frames in the IVB setup was actually lesser than in the Trinity setup. DXVA2CB seems to be taking up more GPU resources than expected in Trinity and that actually results in madVR dropping frames. It is not a memory bandwidth issue because I saw only very slight improvement with DDR3-2133. I wasn't allowed to talk about overclocking in the review, but I will mention here that OCing the GPU is possible and it didn't help in this case.
If you want DXVA2CB + madVR, a discrete GPU is the only solution.
Btw, 1080i60 content is quite common. Most of the BBC documentaries on Blu-ray are encoded in 1080i60 VC-1 IIRC.
Idle power consumption is quite easy to manage with power gating. Once you power gate, leakage power is quite minimal. A difference of few watts can be attributed to environmental factors such as PSU efficiency / chipset efficiency etc. The proper way to judge this would be to measure the CPU package power. HWInfo provides that for Intel CPUs, but AMD doesn't play nice. Only AMD's system monitor program gives a few insights, but, even that is restricted to CPU / GPU load sharing and separate CPU / GPU and memory loads.