Large Catalog Limitations
Hello! I am working on transferring my archive of about 250,000 photos from a large lightroom catalog (taken from 2009-2021) to smaller capture one catalogs. I was planning on separating the catalogs into groups of 5 years. With about 135,000 photos being the maximum number in a grouping.
What are the size limitations of a Capture One catalog? Would 135,000 be too many photos for a given catalog? I would like to know if there will be significant performance hits and if there are any constraints I should be aware of.
Thanks in advance!
-
i was explaining how to make a new version of a existing catalog with probably less problems.
you can also right click on each album and say export as catalog... you ll end up with a new catalog based on the collection.
0 -
Ah, ok.
The point for Thomas is to start with a totally fresh catalog, as he tried already many variants based on an existing catalog, which is to be avoided if assuming that there is an issue incorporated in his catalog.
0 -
I did a few tests exporting original files and importing them into a new catalogue, and it seems to work well, also with variants.
0 -
I found this process pretty reliable too.
Does that mean you will do a test with a big part of your images to verify if the catalog responsiveness is better?
0 -
Yes, I think I'll give it a try with one of my (currently) four catalogues (the one that derives directly from my old main catalogue). I'm curious to see if it makes any difference.
0 -
I've made a new catalogue containing 21k+ images (exported individually and imported into a new catalogue). While it may be marginally faster, I still see some of the same unresponsiveness – for short durations as it's a relatively small catalogue, but nevertheless an indication that the problem is still there – when switching tool tabs, selecting folders/albums, searching/filtering, etc.
0 -
Hi Thomas, that's really a pity.
But at least you can rule out an intrinsic issue in your specific catalog, and you have learned something new.
0 -
@BeO
It was worth trying, and good to know that the issue wasn't caused by this specific catalogue.
@@...
I currently use a MacBook Pro M1 Max with 64GB RAM running macOS 13.5.1. The catalogue and a part of the image files are on the internal SSD drive, the remaining image files are on an external SSD connected by USB-C/USB 3 (I'm not sure about the specific speeds but both SSDs are very fast and I doubt that they're what's causing the unresponsiveness). With this catalogue (containing 21k images) the issue is relatively tolerable, at least it isn't anything like what I saw with my old catalogue (64k+ images), with which Capture One would sometimes become unresponsive for more than a 30 seconds when merely switching tool tabs.
Let me just add too that I've had issues with unresponsiveness in Capture One with different computers/hard drives, different versions of Capture One and macOS, and different catalogues.
0 -
Did you ever have a computer where all images were stored on an internal SSD?
0 -
No, I've had all image files stored on an external drive, but not internally. So far my impression is that it doesn't make any difference where the image files contained in a catalogue are stored. As I remember, Capture One was just as unresponsive when I used an external HDD rather than SSD, even if individual files may have loaded faster with the latter. Also, it doesn't make any difference whether image files are online or offline.
0 -
Assumptions are a good thing, but sometimes they are wrong. Do you have space for 21k images internally?
0 -
Unfortunately I don't have enough space on the internal hard drive. For now, I'll see how it works with my currently four smaller catalogues; at least they don't require the same patience as my old catalogue.
0
Post is closed for comments.
Comments
43 comments