Can you please stop spreading ******** around?
With the 15", both 2017 and 2019, I could use a non-Thunderbolt monitor and it would run perfectly cool as it was running with the internal one. Adding Thunderbolt to the mix added some W of usage but nothing like we are seeing in these 16".
Now, the 16" has some major power usage problems:
1. Firstly the strange 18W state (which we see happens even in clamshell mode with some monitor which shouldn't trigger it, and changing or even upping refresh rates brings it down to 5W). Let's do some comparisons on how much the dGPU consumes with some monitors I have tested:
- 18W for clamshell 2560x1440 60hz, for a total of 221.184.000 pixel being rendered and pushed every second. Note that I didn't have an option to change refresh rate since it was locked at 60. This was using the OFFICIAL Apple HDMI adapter.
- 5W for clamshell 2560x1440 144hz, for a total of 530.841.600 pixel being rendered and pushed every second. This was a different monitor, and I could only get this result by using a direct Thunderbolt>Displayport cable. Using the OFFICIAL Apple HDMI adapter resulted in locking me at 18W still.
Note that according to calculations, we spend roughly 9 times the amount of power we need to spend during the 18W state, using Apple official adapters and cables, with all HDMI monitors. The thing that makes us believe that 18W is a buggy drivers issue is that it's the same threshold it skyrockets up to while the lid is open with an external monitor, and it just stays there: either if you're idle, or moving things on the monitor, or rendering videos, the dGPU just stays at 18W; while working correctly (5W) instead, you can see the power scale up to 6, 8, 10W based on how graphically intensive your workload is.
2. Secondly, we can see there is a power leak inside the chassis for just connecting cables, thing that wasn't happening in the 15" models. In the 15", no matter what, if you didn't connect any Thunderbolt peripherals, the Thunderbolt controller would stay on sleep and didn't consume any power. So with my old 15", I could connect an external USB Hub with HDMI + DisplayPort and the power usage would go up by 0W. If I connect the same hub to the 16W, I see an increase of 3-4W on the Thunderbolt controller on the side it's plugged into. Hell, even if I just plug an USB drive on the left side I have the same power usage.
Just test this: disconnect EVERYTHING from your MacBook, and plug in two lightning cables with NOTHING attached, one on the left side and one on the right side. You will see 3W+3W burned on the Thunderbolt controllers for just attaching inactive cables, for a total of another 6W of heat wasted inside the chassis. This was not happening on the 15".
So, whenever you actually connect an external hub, you're burning 18W for the dGPU and another 3W at least just because you're using a port. At 21W, you have now a permanently hot system even at idle, with batteries always staying warm and ruining themselves, and most of all, you've given up 1/4 of the thermal performance of your brand new 4000$ machine which is always spinning up fans for staying at idle.
Now go and tell me again this was the same for the 15" just because it had a dGPU. You're entitled to have an opinion if you're grasping what we're talking about here, but clearly you don't. Users should be upset and should be reporting the issue to Apple for fixing, not just giving up. And this goes to all the other users continually saying "ThIs Is A cOmMon aNd unFiXabLe ProbLeM wItH MaCBooKs WitH DGPUs!!!"