2013-10-27, 20:55
Hi all
I was checking VDPAU HW acceleration when I found something I was not expecting on MQ5 Skin: While "normal" menus screen (main, setting, etc) used between 16% - 20% of 1 core (Phenom II X4 @ 3GHz), the Showcase view on Movies required 70% (average) of 1 core.
Other statistics: When no display signal is generated (put display to sleep) XBMC CPU use is 10% Top. More "complex" menus (such as weather main screen, Settings->AEON-> Colors) required average of 30%, Albums "Coreflow" view requires 35%, while "Right-List" view requires 45% (average).
I know the more complex the screen layout is, the more CPU it requires, but isn't 70% for Showcase too high? (more taking into account that Coreflow requires only 35%)
All numbers are CPU utilization of XBMC process only (not total CPU consumption) over 1 core (out of 4). I'm using latest Gotham.
Max
I was checking VDPAU HW acceleration when I found something I was not expecting on MQ5 Skin: While "normal" menus screen (main, setting, etc) used between 16% - 20% of 1 core (Phenom II X4 @ 3GHz), the Showcase view on Movies required 70% (average) of 1 core.
Other statistics: When no display signal is generated (put display to sleep) XBMC CPU use is 10% Top. More "complex" menus (such as weather main screen, Settings->AEON-> Colors) required average of 30%, Albums "Coreflow" view requires 35%, while "Right-List" view requires 45% (average).
I know the more complex the screen layout is, the more CPU it requires, but isn't 70% for Showcase too high? (more taking into account that Coreflow requires only 35%)
All numbers are CPU utilization of XBMC process only (not total CPU consumption) over 1 core (out of 4). I'm using latest Gotham.
Max