Comment 0 for bug 1199073

Colin Ian King (colin-king) wrote :

I started up the clock app on a samsung galaxy nexus and I'm seeing:

vmstat 10
procs -----------memory---------- ---swap-- -----io---- -system-- ----cpu----
 r b swpd free buff cache si so bi bo in cs us sy id wa
 0 0 0 102692 24996 193240 0 0 103 4 628 1324 16 9 75 0
 0 0 0 102708 24996 193240 0 0 0 0 1092 2915 17 11 72 0
 0 0 0 102708 24996 193240 0 0 0 0 1059 2850 15 11 73 0
 2 0 0 102708 24996 193240 0 0 0 0 1069 2848 16 11 74 0
 0 0 0 104284 24996 193240 0 0 0 0 1046 2935 16 11 73 0
 2 0 0 104256 25012 193240 0 0 0 6 1019 2812 16 10 74 0

so that's ~2500 context switches/sec above the normal "idle" rate and I'm seeing ~25% of available CPU being burnt just to display a clock. Isn't that a big power hungry?