Wesley wrote:I suppose you can try turning off OpenCL, quit CO, and turning it back on again if you haven't already done so.

Post your CO GPU benchmark in ImageCore. Also what does it list OpenCL and GPU driver version as?

How do I get those scores? I didn't do any systematic benchmarking when I was evaluating. I'm not sure how to turn off OpenCL either, but what would that do anyway? Wouldn't both my onboard Radeon 460 and the external Radeon RX 580 be similarly affected?

OpenCL is in CO Preferences -> General -> Hardware Acceleration

Turning it off and on should have CO benchmark all your GPU and let it know you got a new GPU. You have the monitor connected to the eGPU, right?

Ok, here are my scores. The Blackmagic's benchmark score is under half of what it is for the onboard Radeon 460, which is about what I'd expect based on other benchmarks I've seen. So does this look like the issue I experienced was genuine and not just a case of the eGPU not being utilized? I did get about a 20% boost in export performance.

So GPU only aids in the bottom two (Fit image to screen and Process time). I did some testing on a couple of my machines and clearly Process time benefits greatly from GPU. I find the first bullet a bit wanting saying that Preview Update depends on RAM; I guess that includes CPU speed as well (?).

I think the "Fit Image to Screen" is the key for day-to-day performance when editing. Since this is highly dependent on GPU I would expect the eGPU to help here but it's hard to measure. It may also depend on proper setting of Preview size. If the "fit image" process depends on size of existing Preview, then if you generate unnecessarily large Previews, it could slow the whole process down. I've recently set my previews more appropriately for my iMac and it improved things. I just haven't figured out how to quantify it.

Anyway, my interest is based on a potential move to a laptop based solution with an external 4k monitor (or two) and the eGPU discussion interests me and it's very hard to determine how important GPU, CPU and CPU core count is in real world performance.

EDIT" What's disappointing in this thread is that the eGPU introduced a lag in normal editing and browsing images for one user here. WOuld love ot hear more followup on that.

hyperlinked wrote:Ok, here are my scores. The Blackmagic's benchmark score is under half of what it is for the onboard Radeon 460, which is about what I'd expect based on other benchmarks I've seen. So does this look like the issue I experienced was genuine and not just a case of the eGPU not being utilized? I did get about a 20% boost in export performance.

Unforunately, I've already returned the Blackmagic eGPU so I won't be able to follow your suggestion and see if it helps.

Hopefully the next person who runs into the same issue I did will be able to give this a try and report back if what I experienced was normal or not. If it's not and I can get a serious boost in my culling workflow, I'd consider buying the Blackmagic eGPU again.

This is a late reply which may shed light on hyperlink's problem with the Blackmagic eGPU. I ended up buying an OWC "Helios" eGPU chassis with a Radion "RX" 580 card. I bought both as a package from OWC for $549 (vs $699 for the blackmagic) as the card is virtually identical and you can replace it later on if need be. BTW, The helios chassis appears to be a Sonnet chassis rebranded for OWC.

In using this setup with a 2018 Macbook Pro 13", I noticed that sometimes it worked perfectly with eGPU, and sometimes there was a significant lag when using the eGPU. The lag would appear in various places but the most obvious was when I clicked on different tool tabs, the actual tools below didn't change for a period of time. So if I was on the "Library" tool tab and clicked on "Lens" tool tab, I'd still see the library tools! Eventually the screen would catch up but the effect was awful.

Then I noticed something: when the eGPU behaved badly, it appeared on the bottom of the Activity Monitor "GPU history" graph while the internal Intel Iris Plus 655 appeared above. (In activity monitor, select "window" then "GPU history" or command-4). When it was working perfectly, the eGPU appeared on the top of the "GPU history" graph instead of the bottom.

The difference: it depends what is hooked up when you boot. If you boot away from the eGPU and walk the laptop over to the eGPU then attach it, the problem exists. But if you reboot with the eGPU attached, problem goes away. Seems to be an OS thing to 'prefer' the best GPU attached at boot-time.

I'm running High Sierra 10.13.6 and with Mojave macOS will allow you to select the preferred GPU by app (which I will try when the time comes). But I write this only because it seemed to solve the problem forum member 'hyperlink' was having a couple months ago with the Blackmagic. Overall so far, now that I figured this out, the 13" Macbook Pro with eGPU is stellar. (And it could be better with a more powerful/expensive external GPU card).

I recently upgraded to the Apple MBP 15" 2018 i9 32gb RAM. Top of the line. I saw almost no performance increase in preview generation - this biggest bottleneck to my workflow. I added a Sonnet eGFX Box with Radeon WX9100 (expensive bugger!) and I got a zero increase in preview generation performance. But I also saw no increase in this spec when upgrading my MPB. The published statement that Capture One Pro 12 relies on RAM to generate previews is hogwash. It barely touches the RAM on my system, let alone the processors.

I did a test and observed that Capture One Pro 12 uses 10% of my available 32GB of RAM and 10% of the processing power of my i9 chip when generating previews.

I just wrote the following e-mail to Capture One Support. I would appreciate it if you all write similar notes to them. The squeaky wheel gets the grease! Here is a link to my screen recording that shows the performance issue: https://youtu.be/8_59jtIl71A

Here is the support e-mail:

I recently upgraded to Capture One Pro 12. I also recently upgraded to the mid 2018 MacBook Pro 15 with i9 processor, 32GB RAM, and top of the line specs. Lastly I added a top of the line eGPU (Sonnet eGFX breakaway box 650 + Radeon WX 9100).

After all of these upgrades, I see a nice boost in exporting files from the raw. My system moves at more than double the speed as my previous MBP without eGPU. However, I have zero increase in speed in importing and rendering a new shoot. I often import 1,000 - 2,000 images per shoot, and the preview generation time is quite slow. I noticed that the GPU is not utilized at all for this. This is surprising to me because rendering previews seems to be the perfect task for a GPU.

I did some research and other users are reporting the same conclusions. I also saw an article that you posted that said RAM is the deciding factor in rendering previews. However, I disagree with this, and I would like a better explanation. I doubled the ram and processing power in my MBP and saw no change in rendering previews. Another user compared his 40GB RAM iMac Pro to his MBP with 16GB RAM and way less power, and saw no difference in preview generation time.

On my system, when I observe the apple activity monitor, with only Capture One running, generating previews, I can tell that the GPU is not used at all, and more shockingly, the CPU is only utilized to 10% of its processing power. Lastly, the RAM, which you write on your published paper, is most useful in generating previews, odd as that sounds to me, is also not utilized at all! I have 32GB of RAM, and C1Pro12 uses 10% of that RAM in generating previews!

So, first order of business, please comment on this situation and let me know if I am missing something. Please also explain further why you say that RAM is the determining factor in preview generation performance when my tests show that it has no effect to speak of. Please also explain why a number crunching intensive task like preview generation is only using 10% of CPU power, and no GPU power at all.

Silly question, but do you have Capture One running in a space/window on an external monitor? Or running on your MBP's built-in display?

I think I've read somewhere that eGPU's kinda only boost performance on apps that are running on an external display.

Mark T wrote:I recently upgraded to the Apple MBP 15" 2018 i9 32gb RAM. Top of the line. I saw almost no performance increase in preview generation - this biggest bottleneck to my workflow. I added a Sonnet eGFX Box with Radeon WX9100 (expensive bugger!) and I got a zero increase in preview generation performance. But I also saw no increase in this spec when upgrading my MPB. The published statement that Capture One Pro 12 relies on RAM to generate previews is hogwash. It barely touches the RAM on my system, let alone the processors.

I did a test and observed that Capture One Pro 12 uses 10% of my available 32GB of RAM and 10% of the processing power of my i9 chip when generating previews.

I just wrote the following e-mail to Capture One Support. I would appreciate it if you all write similar notes to them. The squeaky wheel gets the grease! Here is a link to my screen recording that shows the performance issue: https://youtu.be/8_59jtIl71A

Here is the support e-mail:

I recently upgraded to Capture One Pro 12. I also recently upgraded to the mid 2018 MacBook Pro 15 with i9 processor, 32GB RAM, and top of the line specs. Lastly I added a top of the line eGPU (Sonnet eGFX breakaway box 650 + Radeon WX 9100).

After all of these upgrades, I see a nice boost in exporting files from the raw. My system moves at more than double the speed as my previous MBP without eGPU. However, I have zero increase in speed in importing and rendering a new shoot. I often import 1,000 - 2,000 images per shoot, and the preview generation time is quite slow. I noticed that the GPU is not utilized at all for this. This is surprising to me because rendering previews seems to be the perfect task for a GPU.

I did some research and other users are reporting the same conclusions. I also saw an article that you posted that said RAM is the deciding factor in rendering previews. However, I disagree with this, and I would like a better explanation. I doubled the ram and processing power in my MBP and saw no change in rendering previews. Another user compared his 40GB RAM iMac Pro to his MBP with 16GB RAM and way less power, and saw no difference in preview generation time.

On my system, when I observe the apple activity monitor, with only Capture One running, generating previews, I can tell that the GPU is not used at all, and more shockingly, the CPU is only utilized to 10% of its processing power. Lastly, the RAM, which you write on your published paper, is most useful in generating previews, odd as that sounds to me, is also not utilized at all! I have 32GB of RAM, and C1Pro12 uses 10% of that RAM in generating previews!

So, first order of business, please comment on this situation and let me know if I am missing something. Please also explain further why you say that RAM is the determining factor in preview generation performance when my tests show that it has no effect to speak of. Please also explain why a number crunching intensive task like preview generation is only using 10% of CPU power, and no GPU power at all.

eGPUs should also boost performance with only an internal display, although it's not an ideal situation since the bandwidth of T3 is being used going back and forth. Yet, it should boost somewhat the performance.You can see on the video the graphics card is not being addressed by CO12.

NN634969607133502601UL wrote:I think I've read somewhere that eGPU's kinda only boost performance on apps that are running on an external display.

They can definitely boost performance both directions, but as yorickmeijdam mentioned, they're not as efficient as an onboard GPU.

Support of external monitors is an especially hot topic for people with Macbook Pros though. It's because if you have an LG 5K Ultrafine monitor, the only eGPU you can use to accelerate the LG 5K is one of the pricey BlackMagic eGPUs. None of the other eGPUs offer Thunderbolt 3 support that can power a display. Those TB3 ports will only work for peripherals.