Honestly I'd be happy if they could stop Windows 10 from turning my laptop into a hair dryer randomly while it is otherwise entirely idle. The thing is sitting there doing nothing, suddenly the fan will start roaring and the CPU utilization spikes.
Seriously why on Earth does this happen? Even if Edge ends up being more power-efficient the rest of the OS (Windows 10) is going to ensure that I will get no more than 3 hours of battery life on my laptop.
Some interesting optimizations in here, but I'm curious about this one in particular:
> With the Anniversary Update, Microsoft Edge only executes background JavaScript timers once per second in background tabs. More importantly, these timers are coalesced with other work happening across Windows. Microsoft Edge doesn’t wake up the hardware to perform work. Instead we tag along with other work happening across the system, and then quickly yield, allowing the hardware to enter a low power state.
Are there any implications for web techs (maybe like WebTorrent?) that do need to run JS constantly in the background?
In Safari, which slows background JavaScript down or stops it altogether, music stops playing occasionally on Soundcloud when a song ends. The only option to prevent this is to make the Soundcloud tab the sole tab in the browser window. The window can be in the background but the tab is not treated as background tab because it is the active tab in the window.
I'm not sure about Edge in particular, but on most platform runtimes "timers" are separate from IO-availability-triggered asynchronous events. When a WebRTC data connection signals its send channel has become unblocked/receive channel has data available, a handler will be called right then; there's no timer involved. Timers are just for things that have no relevant IO to control them, like animations.
Perhaps they should have cared years ago when this problem was first clear. I don't know about on Windows but on OS X the difference has been massive for years and years.
That's really an Apples to Oranges comparison since Macs and PCs aren't comparable. Yes you could run Windows in BootCamp but it isn't tuned for that and is actually hampered. It would be like making a Surface Pro a hackintosh and using that as a basis for comparison.
There has been a lot of similar work on iOS. Check out the WWDC videos at developer.apple.com a year or more likely two back. It is quite amazing what can be done by schedulers and proper use of resources. I guess these optimizations have also found their way back into macOS and Safari on the laptop platform. Considering the release frequency who knows for sure but at least Apple claims their broswer is very efficient.
It is worth noting that some of the changes go really deep in the architecture and are not easy to pull off. I think lack of system level focus on low battery and the need to do deep changes in the OS are the reasons for the considerable lateness of Microsoft on this front.
Even better, a more standards-efficient browser would reduce the economic resources allocated (by the market) towards ensuring site compatibility across the web, and therefore power.
Apple cares a ton about this for obvious reasons. They want to claim all day use on their products and having s very efficient web browser is a big part of it.
As computing moves from a desktop centric function to a mobile centric function, a more power efficient software should be one of the top design requirements. This is a problem across all platforms.
Imagine if your phone/laptop's full charge lasts for 1 week instead of 1 day.
I wish they didn't do these tests on a Microsoft-made Surface Book...They should've taken a couple of other popular Windows 10 notebooks and maybe do the tests on those. Who knows how much of this difference is because of Edge itself (which is how well it would work on other notebooks, too), and how much it's the optimization they did for Edge for their own hardware.
They say they test across hardware in the article - the Surface Book is the only one they pictured because it's an MS blog and an opportunity to advertise MS hardware.
Besides, I'm pretty sure lowering the number of frames in an animation (among the other fixes/features they mention) is going to pretty much universally lower power requirements.
We chose the Surface Book because it's instrumented with a chip that allows direct measurement of instantaneous power consumption, which most OEM devices don't have, and because it has lots of battery for a fun run-down video :)
re: The reading mode button animation batery use improved
Who needs the button animation at all? I like them not moving, every movement of something that's always on the same place is distracting.
It's stunning on what they spend the energy of the management and the programmers, not only of the CPU's and GPU's of all of us.
"We replaced the traditional XAML animation with a timed GPU transform, and now animate the contents through a viewport – relying entirely on the GPU to perform the work."
Apparently XAML is a traditional way to animate GUI buttons there. Wow.
It's a hint to users that reading mode may provide a better experience. When we introduced it, reading mode usage went up; without the (very subtle) animation, users weren't aware when the feature would be useful.
[+] [-] ams6110|9 years ago|reply
[+] [-] martinml|9 years ago|reply
http://superuser.com/questions/635837/high-cpu-load-from-sys...
In my desktop it was causing it to rev up the fan when it was idle for a few minutes.
[+] [-] Yhippa|9 years ago|reply
[+] [-] slezyr|9 years ago|reply
But it literally rapes my HDD while updating(anytime it wants) or it's AV scanning disk(and you can't turn it off)
It makes my desktops unusable.
[+] [-] executesorder66|9 years ago|reply
Doing nothing, except mabye mining a fuckton of data about you and sending it to Microsoft.
[+] [-] lewisl9029|9 years ago|reply
> With the Anniversary Update, Microsoft Edge only executes background JavaScript timers once per second in background tabs. More importantly, these timers are coalesced with other work happening across Windows. Microsoft Edge doesn’t wake up the hardware to perform work. Instead we tag along with other work happening across the system, and then quickly yield, allowing the hardware to enter a low power state.
Are there any implications for web techs (maybe like WebTorrent?) that do need to run JS constantly in the background?
[+] [-] tqkxzugoaupvwqr|9 years ago|reply
[+] [-] derefr|9 years ago|reply
[+] [-] oakwhiz|9 years ago|reply
[+] [-] zZorgz|9 years ago|reply
Perhaps Edge will a nice competitive impact on the Windows side :P.
[+] [-] MBCook|9 years ago|reply
[+] [-] fsiefken|9 years ago|reply
[+] [-] sp332|9 years ago|reply
[+] [-] kraftman|9 years ago|reply
[+] [-] gtirloni|9 years ago|reply
[+] [-] JBiserkov|9 years ago|reply
[+] [-] adrianlmm|9 years ago|reply
I'm using extensions.
[+] [-] sumitgt|9 years ago|reply
[+] [-] partiallypro|9 years ago|reply
[+] [-] personjerry|9 years ago|reply
[+] [-] cptskippy|9 years ago|reply
[+] [-] heisenbit|9 years ago|reply
It is worth noting that some of the changes go really deep in the architecture and are not easy to pull off. I think lack of system level focus on low battery and the need to do deep changes in the OS are the reasons for the considerable lateness of Microsoft on this front.
[+] [-] kalleboo|9 years ago|reply
[+] [-] ohitsdom|9 years ago|reply
[+] [-] MikusR|9 years ago|reply
[+] [-] theseatoms|9 years ago|reply
[+] [-] talles|9 years ago|reply
[+] [-] MBCook|9 years ago|reply
[+] [-] unknown|9 years ago|reply
[deleted]
[+] [-] yitchelle|9 years ago|reply
Imagine if your phone/laptop's full charge lasts for 1 week instead of 1 day.
[+] [-] j45|9 years ago|reply
[+] [-] ygra|9 years ago|reply
[+] [-] piyush_soni|9 years ago|reply
[+] [-] slyrus|9 years ago|reply
[+] [-] tapirl|9 years ago|reply
- a Windows 8 lover.
[+] [-] growthape|9 years ago|reply
[+] [-] edrobap|9 years ago|reply
[deleted]
[+] [-] mtgx|9 years ago|reply
[+] [-] eightysix_four|9 years ago|reply
Besides, I'm pretty sure lowering the number of frames in an animation (among the other fixes/features they mention) is going to pretty much universally lower power requirements.
[+] [-] kylealden|9 years ago|reply
[+] [-] cheeze|9 years ago|reply
Still a mediocre browser though IMO. iamleppert nailed it on the head.
[+] [-] zeta0134|9 years ago|reply
[+] [-] acqq|9 years ago|reply
Who needs the button animation at all? I like them not moving, every movement of something that's always on the same place is distracting.
It's stunning on what they spend the energy of the management and the programmers, not only of the CPU's and GPU's of all of us.
"We replaced the traditional XAML animation with a timed GPU transform, and now animate the contents through a viewport – relying entirely on the GPU to perform the work."
Apparently XAML is a traditional way to animate GUI buttons there. Wow.
[+] [-] kylealden|9 years ago|reply