In terms of the dGPU driver issue causing kernel panics. Apparently engineers are working on a fix.Are there any feedback from Apple about this?
In terms of excessive power draw. They probably don’t care enough.
In terms of the dGPU driver issue causing kernel panics. Apparently engineers are working on a fix.Are there any feedback from Apple about this?
In terms of the dGPU driver issue causing kernel panics. Apparently engineers are working on a fix.
In terms of excessive power draw. They probably don’t care enough.
I understand that unidirectional computation (eg. gaming) has less latency than bidirectional computation, but that’s true for both the dgpu and egpu. The question was regarding the difference between the egpu and dgpu performance—namely, how/why the stronger egpu can have worse performance in some cases than the weaker dgpu. Obviously bandwidth is the other key difference here, so I assume that is the culprit. But what I’m stuck on is that Xnorth said the bidirectional data is the reason the egpu is hitting the bandwidth cap. But with full duplex, as I understand it, bidirectional computation in and of itself should have no bearing on whether or not the cap is hit. In other words, even unidirectional computation (gaming) should be able to get faster results on the dgpu than the egpu, if the task is demanding enough to cause the egpu to hit the bandwidth cap, yet the dgpu is able to perform that task higher than that cap.Computational work requires a round trip is all he means. It's simple to understand. The data has to go from your computer, to the eGPU, and then back. This adds latency because it can only travel at the speed of light + whatever time it takes to compute.
When you're playing a video game it's just sending data to the eGPU to display through its native DP/HDMI port so it isn't affected in the same way.
I’m a little more confused now by what you’re saying. Are you now saying bidirectional data isn’t causing it to max out the bandwidth? Because that was the part that tripped me up. Like I said to the person above (to quote myself), “with full duplex, as I understand it, bidirectional computation in and of itself should have no bearing on whether or not the cap is hit. In other words, even unidirectional computation (gaming) should be able to get faster results on the dgpu than the egpu, if the task is demanding enough to cause the egpu to hit the bandwidth cap, yet the dgpu is able to perform that task higher than that cap.”Latency. Being full duplex doesn't eliminate latency caused by the eGPU, which becomes an another step, or bottleneck, that reduces the bandwidth. A GPU on the motherboard has a direct PCIe connection to the CPU so it's more efficient. An eGPU's processing power is cut by as much as 20% compared to it connected directly to the motherboard.
Likely doing spotlight indexing and other new maintenance tasks..give it a few days after restore, migration or app installs.I’ve received my 2.3/64GB to replace my 2.4/32GB, both refurbs. Interesting to see that the 2.3 seems to idle some 10 degrees higher than the 2.4 and get hot with very little activity. I’ll let everything settle down but seems odd, especially as the 2.3 is a slower chip.
I understand that unidirectional computation (eg. gaming) has less latency than bidirectional computation, but that’s true for both the dgpu and egpu. The question was regarding the difference between the egpu and dgpu performance—namely, how/why the stronger egpu can have worse performance in some cases than the weaker dgpu. Obviously bandwidth is the other key difference here, so I assume that is the culprit. But what I’m stuck on is that Xnorth said the bidirectional data is the reason the egpu is hitting the bandwidth cap. But with full duplex, as I understand it, bidirectional computation in and of itself should have no bearing on whether or not the cap is hit. In other words, even unidirectional computation (gaming) should be able to get faster results on the dgpu than the egpu, if the task is demanding enough to cause the egpu to hit the bandwidth cap, yet the dgpu is able to perform that task higher than that cap.
Yes it was posted, and rated trash as it should be. He's curing the symptoms and not the causes, which is basically the same as taking cough syrup and continue to ignore the fact you got COVID-19.Hey all! First time poster and sitting on an older 2015 Macbook Pro. Am very close to pulling the trigger on a new 16" Pro but I will need the new 16" Pro to drive two external 49" ultra wide monitors, so this issue is making me hesitate on the upgrade at the moment.
Has this link ever been posted in this thread yet?
How to FIX your 16” MacBook Pro - (Don’t Return it)
Explains why the fans run much faster and often than in the older 2015 Macbook Pro. Basically the 16" Pro is designed to run much cooler than the older 15" Macbook Pro, which results in the significant increased fan usage. There are software tools available to to override this feature and configure it to run the same as the 2015 Macbook Pro.
I don't think this itself explains the crazy wattage increases from the dGPU when using external monitors though, but thought some might find it helpful.
macOS Catalina 10.15.5 Release Notes | Apple Developer Documentation
Update your apps to use new features, and test your apps against API changes.developer.apple.com
Resolved Issues :
- Large data transfers to RAID volumes no longer cause Finder to become unresponsive. (61307708)
Not holding my breath, how can Apple stay silent for this long? The issue was also first reported last November on discussions.apple.com
A small ray of sunshine...
I've been emailing CalDigit customer support around two issues related to the 10.15.4 update. They are: CalDigit's firmware update tool no longer works as of 10.15.4, and frequent kernel panics on wake when connected to the CalDigit TS3+ (which only started in 10.15.4). CalDigit recently provided the following update (in relation to the kernel panic):
We just got reminded by our engineer that we have seen this behaviour with several customers on the 16” MacBook Pro which is caused by Apple’s GPU driver. We have contacted Apple regarding this and a fix is in the works. However, due to the COVID-19 situation, this might be a bit delayed. We would recommend to stay updated with macOS as this should be resolved with a new macOS update.
This gives me some cause for hope that Apple is indeed addressing GPU driver issues.
Hooray.
Did you see this post in that forum? I'll quote it below and it's not my post:
Hello everyone, I posted the following over at the Apple Support Communities but I'm reposting it here in case anyone may be interested...
-----------------------------------
This is not a solution. I am presenting my observations when using it with an external 4K monitor, and it is intended for those of us who decided to stick with their 16-inch and live with it for the time being, and just want to hear how others are doing.
My setup:
MacBookPro (16-inch, 2019) / 2.6GHz 6-Core Intel Core i7 / 32GB RAM / AMD Radeon Pro 5300M 4GB
External 4K monitor (LG 27UD68-P)
The resolution of the MBP is set to Looks like 1536 x 960.
The resolution of the external monitor is set to Looks like 1920 x 1080.
Connection: 3rd party USB-C to DisplayPort cable on the left side of the MBP (more on this later)
(I also have a USB-C to HDMI adapter but it didn't make a noticeable difference.)
We all know that many of our MBP exhibits this behavior where the RPM of the fans tend to increase (and the GPU uses more watts) when using it with an external monitor, unless used in clamshell mode.
The following graph from iStat shows the speed of my MBP's left fan under different conditions, when using both the internal monitor and an external 4K monitor.
View attachment 912850
While it is pretty self-explanatory, I want to point out the following observations:
I also used FCPX and observed that:
- When the MBP is idle (the flat slope right before [2] in the image), the fans spin at about 2300RPM, and personally I think that this is acceptable.
- Even when doing light web browsing, it is under 3000RPM.
- Watching a Youtube video (the Hermitage video on Apple's channel) at point [5] increases the fan speed but then it starts to stabilize at around 3300RPM (subjectively speaking, this is when I start to notice the sound of the fans).
Lastly, I want to point out that, at least in my setup, plugging the monitor cable on the left side of the MBP reduced the fan speed by roughly 400RPM compared to plugging it on the right side. This is independent of where the charging cable is being used.
- When editing/playing back footage, the fans spin at about 3000~4000RPM.
- When analyzing/exporting footage, the fans spin at about 4000~5000RPM.
- If I do the same things in clamshell mode, these speeds are roughly reduced by 1000RPM.
- However, the task of analyzing/exporting a video footage is a computationally expensive task, and it will nevertheless hit 5000RPM even in clamshell mode.
I am attaching the sensor readings from iStat in case anyone wants to compare it with their own.
This is at point [2] in the previous image, where the system was pretty much idle.
If you have any questions, please let me know.
View attachment 912851
144 Hz | 18 W |
120 Hz | 18 W |
99.88 Hz | 5 W |
74.88 Hz | 5 W |
60 Hz | 18 W |
59.88 Hz | 5 W |
50 Hz | 5 W |
On my LG 34UC79G connected via DisplayPort at either native resolution 2560x1080 or the slightly lower 2048x864 I get these "Radeon High Side" measurements when the lid is closed:
144 Hz 18 W 120 Hz 18 W 99.88 Hz 5 W 74.88 Hz 5 W 60 Hz 18 W 59.88 Hz 5 W 50 Hz 5 W
I can't explain why at 60 W it draws almost 4x as much power compared to the much more resource intensive 99.88 Hz.
At 1920x1080 the only options are 50 Hz and 60 Hz and both draw only 5 W.
But when the lid is open, it's 18W, always, in every configuration, in every resolution.
To compare, on my late 2016 MacBook Pro I get only 11 W with the lid open and external display at 120 Hz. And the fans run at their absolute minimum of ~2000 rpm, completely silent.
Massive step back considering that I only wanted to upgrade because the battery started to bulge on my old one!
I don't want to make any speculations, but it looks like that is the case. According to another user in the Apple Support Communities, that person was told by CalDigit that Apple is aware of this issue and is working on a fix. Of course, we still can't party until such a fix is officially released.I find it interesting that you are experiencing the issue on the i7/5300m model. So appears to not be cpu/gpu specific. Must be a driver issue surely?
I have a guess. USB-C monitors which charge MacBook pro, I suppose the fan noise won't happen with these monitors. What do you think?
What about Thunderbolt display?Not true at all. They all exhibit similar behaviours.
As far as I know it doesn't matter what display, what resolution, what cable, if HDMI or USB C - nothing matters with the MBP 16", except if it is in clamshell - but even then the right refresh rate must be set. So in short:What about Thunderbolt display?
I think there is a case where someone used x2 LG 4k UltraFine monitors (daisy chained and in clamshell) and I wouldn't trigger the 18-20Watts but other than that it seems to make no difference with open lid.What about Thunderbolt display?
On my LG 34UC79G connected via DisplayPort at either native resolution 2560x1080 or the slightly lower 2048x864 I get these "Radeon High Side" measurements when the lid is closed:
144 Hz 18 W 120 Hz 18 W 99.88 Hz 5 W 74.88 Hz 5 W 60 Hz 18 W 59.88 Hz 5 W 50 Hz 5 W
I can't explain why at 60 W it draws almost 4x as much power compared to the much more resource intensive 99.88 Hz.
At 1920x1080 the only options are 50 Hz and 60 Hz and both draw only 5 W.
But when the lid is open, it's 18W, always, in every configuration, in every resolution.
To compare, on my late 2016 MacBook Pro I get only 11 W with the lid open and external display at 120 Hz. And the fans run at their absolute minimum of ~2000 rpm, completely silent.
Massive step back considering that I only wanted to upgrade because the battery started to bulge on my old one!
So in short:
MBP 16" with external monitor and not in clamshell = 18+ W
MBP 16" with external monitor in clamshell + the right settings/refresh rate = about 5W.