16" MBP CPU/GPU performance
Seems like V20 is at least taking advantage of more of the power available to it than 12 did. Still seems like there's work to be done though. This is importing to a catalog in place. Originals on a Thunderbolt 3 M.2 SSD RAID, catalog on internal SSD. Top CPU/GPU/VRAM, 32GB RAM.
http://matthewcohen.org/CPUGPU_V20_Import.png
http://matthewcohen.org/CPUGPU_V20_Import.png
0
-
HI have been testing it on an older MacPro 5.1 with 12 cores and a Vega 56.
I am dealing professionally with rather large numbers of files.
I got similar results. CPU and GPU are barely used when I try to import images keeping them in the same location. Dreadfully slow, Capture One barely useable during the import period and the hardware nowhere near maxed out.
Sloppy programming I guess.0 -
BerndInBerlin wrote:
Sloppy programming I guess.
You dont need to guess 😊 Not only a sloppy programming, CO uses a dated version of OpenCL (which is not supported by Apple any more) and the team is refusing to utilize Metal framework.0 -
fatihayoglu wrote:
BerndInBerlin wrote:
Sloppy programming I guess.
You dont need to guess 😊 Not only a sloppy programming, CO uses a dated version of OpenCL (which is not supported by Apple any more) and the team is refusing to utilize Metal framework.
Interesting. But even with OpenCL my Vega card should see some action.0 -
http://matthewcohen.org/beachball.png
beachballing on open. barely touching anything.0 -
May I ask how many images you are trying to import? I just started another thread here pointing at the horrible performance with large numbers of files even on high spec computers - and I just saw that you are on it already.
Curios to hear how it works out for you with 130k images. I don't have high hopes...0 -
I have the same experience on my brand new MBP 16" (64GB RAM, Radeon 5500 8GB ). C1 v20 feels in no way quicker or rather more laggy than v12 on my old MBP from 2015 with much lesser specs. The core of the software is clearly not optimized to take advantage of powerful GPU that's inside modern Macs. Meanwhile in DaVinci Resolve I can scrub through 4K RAW footage like its nothing.
Instead of constantly adding more bells and whistles I would appreciate if they'd overhaul the core of the software to just be operating at maximum speed. Because that is what makes the biggest difference in the life of professionals. New color editor and fancy layer tool etc is cute but really I couldn't care less if it takes 2 secs for each preview to be rendered when doing image selection and the client next to me is losing its patience (on a brand new speed out 5000€ Macbook!).0 -
BerndInBerlin wrote:
May I ask how many images you are trying to import? I just started another thread here pointing at the horrible performance with large numbers of files even on high spec computers - and I just saw that you are on it already.
Curios to hear how it works out for you with 130k images. I don't have high hopes...
it ended up taking about 4 days to "import" which is funny because the files didn't have to move anywhere. many crashes, and a solid 30 hours of drawing previews. everything is in there now, and the previews are done drawing. beachball for minutes at a time even though it is not doing anything at all. can not scroll through the full 130k thumbnails even without crashing that takes ~20 min to recover from. there's no way this software is designed/tested for libraries more than 100k pictures.
i don't want to have to manage my software, that's what software is for. they are 100% telling us that this software is not for us.0 -
d42b wrote:
Instead of constantly adding more bells and whistles I would appreciate if they'd overhaul the core of the software to just be operating at maximum speed. Because that is what makes the biggest difference in the life of professionals. New color editor and fancy layer tool etc is cute but really I couldn't care less if it takes 2 secs for each preview to be rendered when doing image selection and the client next to me is losing its patience (on a brand new speed out 5000€ Macbook!).
they've told us for years, through inaction, that this software is not for volume.
right now i have Photo Mechanic Plus and C1 both pointed at the same folders. you want to see just how bad C1 is at this, try doing anything in PMP and then a similar action in C1. what a joke.0 -
Wow. There are quite some people having the same problems. Funny on the other thread someone pointed out that it wouldn't be important for the majority...
They clearly don't have to deal with large numbers of images.
I actually use Lightroom as my go to app to run my archive of the last few years living on a server. At present it's handling almost 600000 images without a problem. Can't even imagine that in C1 as I had similar experiences like mattcohen and will never attempt again to use C1 for a large image archive.
We are all paying pretty serious money and I really feel the functions implemented should work properly as it is the case with any other professional software. The limit should be the provided hardware and not poor coding.0 -
I've been watching C1 20 performance on my 2019 MBP (8-core i9, Pro Vega 20, 32 GB RAM, Mojave) and am seeing slightly more GPU usage than C1 12 had, but it's still nowhere near what C1 12 did on my old MBP running Sierra.
As I've reported on a couple of threads here, forcing the GPU greatly improves performance. I force using gfxCardStatus (old software), and it can also be done by turning off "Automatic graphics switching" in the Energy Saver pref pane. Unfortunately I haven't figured out how to do this with my 2012 Mac Pro.
I wonder why Phase One seems so reluctant to use Metal, other than that it's Mac specific and they're trying for as much platform-common code as possible. Another example: they still don't completely support long-standing Mac file selection methods (example: discontiguous groups of files).
Anyway, go back and try forcing the GPU and see what happens. And of course, return to normal use when you're done with C1.0 -
Hm. My testing shows that GPU is actually properly utilised during export, especially JPGs.
The problem described here seem to be within the DAM part of Capture one. The basic functionalities like import and creating previews has always been weak. So not sure anything can be done from the user side.0
Post is closed for comments.
Comments
11 comments