Linked by Thom Holwerda on Wed 19th Apr 2017 20:36 UTC

Most people running Windows like having multiple apps running at the same time - and often, what's running in the background can drain your battery. In this latest Insider Preview build (Build 16176), we leveraged modern silicon capabilities to run background work in a power-efficient manner, thereby enhancing battery life significantly while still giving users access to powerful multitasking capabilities of Windows. With "Power Throttling", when background work is running, Windows places the CPU in its most energy efficient operating modes - work gets done, but the minimal possible battery is spent on that work.

My biggest worry with technology like this is that it affects unsaved work. Luckily, you're supposed to be able to turn it on and off.

Permalink for comment 643234
To read all comments associated with this story, please click here.
RE[3]: Comment by tidux
by grahamtriggs on Thu 20th Apr 2017 14:27 UTC in reply to "RE[2]: Comment by tidux"
Member since:

The priority classes are only going to work if the application detects whether it should be in an idle state, and changes it's priority.

Depending on user permissions, it may not be allowed to change it's priority.

Then you get all sorts of interesting cases - if a window is visible (e.g. it's the only 'application' running), but it doesn't have focus (user has clicked on the explorer, or dismissed an alert) - should that application consider itself a background application or not?

There is an argument that the application should be allowed to know best - but it's also a ton of effort for developers to be building such determination into everything they write.

Having something sensible in the OS that takes that burden from the application developer is a good thing, along with user controls to override if necessary. Possibly even better if there are APIs that let the application take control when the developer knows that is likely to be needed.

Reply Parent Score: 1