Discussion - Allow users to put individual tabs to sleep

I'm trying really hard to think of more than 5 use cases where it's useful to have web pages do anything that consumes ANY CPU when they're not in focus. Mostly my browser converts electricity into ads in windows I'm not looking at. For all the hours I leave my PC unattended, 80% of the electricity just goes right to edge which converts it into ads!

It feels like it's very silly that at the core, web pages can eat up cpu and gpu when they're NOT being used. I feel like, unless a web page is focused, the default should be a complete shut down of that tab, clip the available CPU to ZERO, and then we work backwards from there. We find rules that allow tabs to be "ON" instead of figuring out rules for turning the tabs OFF.

Here's my view from the ground floor, (and this is using the Dev channel so I know results may vary): I have 6 tabs open and visible right now and cpu usage of 20%, GPU usage of 30%, and 2.8GB ram used. Now, I do have 100 or so hidden (non-active) tabs (most of them are shown as "unloaded" in edge:\\discards) but I have to assume signals from those tabs are still eating resources. (last patch it was 8GB of RAM, so I appreciate the improvements!). It would be unimaginable if only 6 visible windows were doing that.  

But why do we default to giving inactive pages the ability to do all of, lets face it, play ads while we're not focused on the page?