GPU automatic graphics switching not working?
Capture One Pro does not appear to use the late 2018 MacBook Pro's Radeon Pro Vega 20 GPU when automatic graphics switching is selected. If automatic graphics switching is turned off, the Vega 20 GPU is used and the Pro Vega 20 GPU monitor frequently spikes to the max (as shown while monitoring GPU history in Activity Monitor). I need to determine the if automatic switching does should work with Capture One and when it should. Photos automatically makes use of the Vega 20 GPU, so it seems the issue is related to Capture One, not the GPU.
How I determined that switching is not automatically occurring: Turned on automatic GPU switching and did various edits and preview regeneration in Capture One and did not see any use of Vega 20 GPU.
Questions: What does it take for Capture One to automatically switch to the Pro Vega 20 GPU? Which of these seems likely: The Pro Vega 20 is unneeded for Capture One's best performance on the MacBook Pro, I am not doing anything that requires it, or automatic switching does not work. What would be the proper way to test to see if Capture One is able to automatically switch to the Pro Vega 20?
I have also submitted a support case for this issue, but wondered if any forum readers have previously dealt with this issue and found an easy answer.
How I determined that switching is not automatically occurring: Turned on automatic GPU switching and did various edits and preview regeneration in Capture One and did not see any use of Vega 20 GPU.
Questions: What does it take for Capture One to automatically switch to the Pro Vega 20 GPU? Which of these seems likely: The Pro Vega 20 is unneeded for Capture One's best performance on the MacBook Pro, I am not doing anything that requires it, or automatic switching does not work. What would be the proper way to test to see if Capture One is able to automatically switch to the Pro Vega 20?
I have also submitted a support case for this issue, but wondered if any forum readers have previously dealt with this issue and found an easy answer.
0
-
I did some testing and found:
Initial startup of Capture One is single threaded (1 CPU)
It appears that Importing files and building previews doesn't use the GPU other than for screen updates. Very heavy on CPU for previews. (Files were imported from the Desktop, not a card since I didn't want to get into USB performance...)
Editing uses the GPU but it's hard to run a repeatable test. Exporting and Output Recipes use the GPU, although it seems to be limited by CPU. I ran the same files on a 2015 27" Retina iMac, a 2017 15" MacBook Pro and a 2018 15" MacBook Pro and could see with the 4 core 2017 MacBook the eGPU was not at full utilization where it was on the 6 core 2018 MacBook Pro. I also did the Sonnet Breakaway Puck 570 eGPU on the two MacBook Pros.
I ran both IQ180 80 MB files and Olympus E-M1 MkII 20 MB files. To my surprise the performance was noticeably better on the IIQ files across the board. Duh, of course Phase One optimizes best for their own backs!
I used Activity Monitor to see what the GPUs were doing. This is not by any means a comprehensive or scientific performance test, but it is interesting. I was underwhelmed with the Vega 20 compared to the AMD 560 - I think that upgrade wasn't worth the money (relating to Capture One, at least.) The Sonnet 570 eGPU was a noticeable performance boost.
Phase One people please feel free to comment!
iMac (Retina 5K, 27-inch, Late 2014)
3.5 GHz Intel Core i5 (quad core)
32 GB 1600 MHz DDR3
AMD Radeon R9 M290X 2048 MB
3 TG Fusion drive
Mojave 10.14.2
Capture One Pro 12 v 12.0.0.270
Import 199 IQ180 files - 13.2 sec
Build previews - 9 min 21 sec
CPU intensive used < 8 GB RAM
Export to 16 bit pdf - 6 min 29 sec
Maxed GPU, < 13 GB RAM
Import 199 ORF files (Olympus E-M1 Mk2) - 14.6 sec
Build previews - 11 min 28 sec
CPU intensive used < 7 GB RAM
Export to 16 bit pdf - 8 min 10 sec, < 13 GB RAM
MacBook Pro (15-inch, 2018)
2.9 GHz Intel Core i9 (6 core)
32 GB 2400 MHz DDR4
Radeon Pro Vega 20 4080 MB
Intel UHD Graphics 630 1536 MB
1TB SSD
Mojave 10.14.2
Capture One Pro 12 v 12.0.0.270
Import 199 IQ180 files - 14 sec
Build previews - 2 min 4 sec
CPU used < 8 GB RAM
Graphics disabled (Hardware Acceleration off in C1)
Export to 16 bit pdf - 7 min 44 sec
Automatic Graphics Switching Enabled
Export to 16 bit pdf - 4 min 59 sec
Some GPU, < 11 GB RAM
Used Intel 630 only
Automatic Switching Disabled
Export to 16 bit pdf - 4 min 58 sec
Maxed GPU, < 11 GB RAM
Used Intel 630 and Vega 20
Automatic Graphics Switching Enabled, RX570 eGPU
Export to 16 bit pdf - 4 min 16 sec
Some GPU, < 11 GB RAM
Used all three GPUs
Automatic Graphics Switching Enabled, RX570 eGPU, External GPU preferred set
Export to 16 bit pdf - 4 min 42 sec (too much overhead with three GPUs?)
Some GPU, < 18 GB RAM
RX570 maxed
Import 199 ORF files (Olympus E-M1 Mk2) - 15.7 sec
Build previews - 3 min 54 sec
CPU intensive - used < 19 GB RAM
Automatic Graphics Switching Enabled
Export to 16 bit pdf - 6 min 12 sec
Some GPU, < 19 GB RAM
Used Intel 630 only
Automatic Switching Disabled
Export to 16 bit pdf - 6 min 08 sec
Maxed GPU, < 19 GB RAM
Used Intel 630 and Vega 20
Automatic Graphics Switching Enabled, RX570 eGPU
Export to 16 bit pdf - 6 min 09 sec
Some GPU, < 20 GB RAM
Used all three GPUs
Automatic Graphics Switching Enabled, RX570 eGPU, External GPU preferred set
Export to 16 bit pdf - 4 min 55 sec
Some GPU, < 18 GB RAM
RX570 maxed
MacBook Pro (15-inch, 2017)
2.9 GHz Intel Core i7 (quad core)
16 GB 2133 MHz LPDDR3
Radeon Pro 560 4096 MB
Intel HD Graphics 630 1536 MB
500 GB SSD
Mojave 10.14.2
Capture One Pro 12 v 12.0.0.270
Import 199 IQ180 files - 17 sec
Build previews - 2 min 32 sec
CPU intensive - used < 9 GB RAM
Automatic Graphics Switching Enabled
Export to 16 bit pdf - 6 min 39 sec
Some GPU, < 10 GB RAM
Used Intel 630 and 560
Automatic Switching Disabled
Export to 16 bit pdf - 6 min 33 sec
Maxed GPU, < 10 GB RAM
Used Intel 630 and 560
Automatic Graphics Switching Enabled, RX570 eGPU
Export to 16 bit pdf - 5 min 18 sec
Some GPU, < 10 GB RAM
Used all three GPUs
Automatic Graphics Switching Enabled, RX570 eGPU, External GPU preferred set
Export to 16 bit pdf - 5 min 32 sec
Some GPU, < 18 GB RAM
RX570 maxed
Import 199 ORF files (Olympus E-M1 Mk2) - 18.7 sec
Build previews - 4 min 43 sec
CPU intensive - used < 8 GB RAM
Automatic Graphics Switching Enabled
Export to 16 bit pdf - 8 min 45 sec
Some GPU, < 10 GB RAM
Used Intel 630 and AMD 560
Automatic Switching Disabled
Export to 16 bit pdf - 8 min 55 sec
Maxed GPU, < 10 GB RAM
Used Intel 630 and Vega 20
Automatic Graphics Switching Enabled, RX570 eGPU
Export to 16 bit pdf - 6 min 44 sec
Some GPU, < 10 GB RAM
Used all three GPUs
Automatic Graphics Switching Enabled, RX570 eGPU, External GPU preferred set
Export to 16 bit pdf - 7 min 28 sec
Some GPU, < 9 GB RAM
RX570 almost maxed (throttling for heat?)0 -
How disappointing regarding the benefits of the Vega 20 on the MacBook Pro for Capture One. Viewing the GPU history in Activity Monitor, I would at least like to have been able to see the Vega 20 used with automatic switching on. Maybe Capture One is not demanding enough to trigger automatic switching to the Vega 20 or it just doesn't show in the history window. Oddly, Photos auto switches to the Vega 20 for almost any edit.
As Phil says, maybe an underwhelming investment, but if nothing else, there's the pride of ownership.
Jerry0 -
[quote="NN635680879799322049UL" wrote:
(...)
, but if nothing else, there's the pride of ownership.
I have to remember that 😁0 -
The support staff responded to my original question about apparent failure of autoswitching of the GPUs on my MacBook Pro. They suggested deleting the Image Core files (they regenerate when COP is reopened) and checking the function of Open CL (focus mask turns off when moving the Exposure and other sliders when it is working). I did this, and my Radeon Pro Vega 20 GPU still did not show activity (as reflected by the GPU history in Activity Monitor) during various maneuvers, such as regenerating previews, while the integrated Intel GPU handled all of the processing as long as autoswitching was on.
I reiterated this to the support staff and they say while both GPUs are used for computing, the only thing reflected by by the GPU history window is the extent to which each GPU is driving the screen display, not the computational load. This makes it hard to compare the integrated GPU to the Pro Vega 20.
So, we have to take it on faith that both GPUs are being used. While one can make the use of the Pro Vega 20 mandatory by turning off autoswitching, there does not seem to be a way to turn off the Pro Vega 20 and make the integrated Intel GPU handle the entire load. Thus, results of speed tests with and without autoswitching, should not differ since you cannot turnoff the higher performing GPU. This seems to be true, given some of the timings are a tiny bit slower with autoswitching turned off, thereby excluding the integrated Intel GPU's contribution.
Therefore, the Pro Vega 20 may not be a worthless purchase. You just can't test it with the software built into the MacBook Pro. There is an app called gfxCardStatus that will turn on each GPU separately.0 -
I have the same issue on my MacBook Pro 2017 with Radeon Pro 460. COP simply does not use the discreet graphics unless automatic switching is turned off. It beats me why they refuse to acknowledge and fix the problem for such a long time.
There is a visible, clear and present difference in performance when editing images. I need to remember to manually switch off automating graphics switching every time I use COP. Seriously...0 -
It may be a battery life issue. I’ve noticed that the Vega 20 really sucks the battery down even when just driving the screen. I decided turning the autoswitching on and off depending on when I’m on battery is worthwhile. Interestingly enough, when I’m plugged into my eGPU and monitor the eGPU is assigned to the monitor and the Vega 20 is assigned to the laptop screen even though the autoswitching is on. Now that I’ve figured out how to force the configuration to what I want when I want it. I’m OK with it, but it sure was a pain getting there! 0 -
I uave the same issue with MBP 16 radeon 5500, gpu not switching automaticaly.
0
Post ist für Kommentare geschlossen.
Kommentare
7 Kommentare