Skip to main content

⚠️ Please note that this topic or post has been archived. The information contained here may no longer be accurate or up-to-date. ⚠️

Any tips for speeding up large catalog?

Comments

7 comments

  • Ian Wilson
    Moderator
    Top Commenter
    You might like to explore this with Support, sending them log files, etc. Many users don't find it slows to a crawl with a catalog that size, so they might be able to help you identify whether there is any particular feature in your set-up that exacerbates the problem.

    Ian
    0
  • Andy Nickless
    It might be worth reducing the preview size of your files. The default size is quite large (2560px).

    Try reducing them (in Preferences) to about 1440, then select all the images in your library and Regenerate the Previews (Image > Regenerate Previews) to see whether that makes a difference. If it doesn't, you can always increase the default size and regenerate again.
    0
  • Ian Wilson
    Moderator
    Top Commenter
    Except that 1440 is unlikely to be a good size to work with. If the previews aren't large enough for Capture One to display at the fit-to-screen zoom level, it has to refer back to the raw file to generate something on the fly for you to see when you select an image and try to view it - which will slow things down.

    Ian
    0
  • Andy Nickless
    Good point, Ian - thanks.
    Keep the viewing window small enough to view the preview at 1440 then??
    Andy
    0
  • mli20
    NNN637071635549120417 wrote:
    Have a catalog with 15000 photos. Just opening all images, let alone filtering makes things slow to a crawl, especially when first opening the program. Previews are already generated.

    I have an i5-8600k overclocked and 16gb ram, catalog is on an SSD, and storage drives run in parallel with drivepool so should be faster than a normal single HDD.

    REALLYYYYYY want to ditch Lightroom but good Lord it's so much faster at viewing large catalogs

    fedloan'> irs.gov easybib



    If you find any merit to the discussion found here "Performance re. keywording,..." at
    0
  • Ian Leslie
    I also have issues with performance and the all images collection. I have an open case on that now (I owe them some information).

    Getting an appropriate preview size was one of the first things we looked at and it did help but in no way resolved it.

    I tend to not spend a lot of time in the All Images collection anyway so I am not suffering a lot and I have worked around it by creating smart albums for each year I have images in my catalogue. Usually when I am looking for something I have a year or three time window where I think it is.

    My machine is much lower spec than yours. Windows 10 on an i5 with 16Gb and an HDD for the catalogue and images and an SSD only for the app and the OS.
    0
  • Bud James

    I've been using C1P for about 3 years. My Lightroom catalog had about 150k images. This choked C1P on the import. I ended up having to split my LR catalog into several smaller C1P catalogs to keep the catalog under 20k images. C1P does not like large catalogs, period. I'm running a iMacPro with 64GB RAM, 2TB internal SSD and Thunderbolt 2 connected OWC Thunderblade 8TB SSD. The read/write speeds of the internal SSD averages 2,700-2,900 MB/S while the external SSD averages 2,100-2,300 MB/S. Even with this setup, C1P is sluggish once the catalog exceeds about 20k image.

    Regards, Bud James
    Please check out my fine art and travel photography at www.budjames.photography or on Instagram at www.instagram.com/budjamesphoto

    0

Please sign in to leave a comment.