The Continuous browser activity test is a heavy load test and we would expect normal screen - on life, which includes a lot of short -
term idle time, to match the reported «powercfg» results of over 8 hrs activity over a full days «always - on» usage.
Not exact matches
I wonder how many game developers really spend
time thinking about these pumping
idle stances in
terms of how much is too much.
With the rise of the sharing economy it is easier than ever to latch onto short -
term gigs, especially if you have a strong Internet connection and some
idle time.
That is the wrong focus, as recovering from a disaster has a huge cost in
terms of lost customer service,
idle staff
time, and and hits to productivity and customer relations.