Pages: [1]   Go Down

Author Topic: Recommendation on Catalog Capacity  (Read 858 times)

James R

  • Sr. Member
  • ****
  • Offline Offline
  • Posts: 364
Recommendation on Catalog Capacity
« on: January 08, 2016, 01:58:31 pm »

Is there an image capacity at which C1 becomes sluggish?  I created 3 catalogs with approx. 11K images each.  I still have another 80K images to import and would prefer to put them into just one of those 3 catalogs. 
Logged

fdisilvestro

  • Sr. Member
  • ****
  • Offline Offline
  • Posts: 1854
    • Frank Disilvestro
Re: Recommendation on Catalog Capacity
« Reply #1 on: January 08, 2016, 08:32:34 pm »

Hi,

You should not have any issues with 80k images, even if they are all in one catalog. If you experience low performance, try to regenerate the previews (you can delete the content of the "cache" folder)

For large number of images, I would recommend using a catalog with referenced imaged, not managed, as it gives you the flexibility of where you store your images:

Example of a possible scenario:
- C1 catalog + previews + adjustments on a fast SSD
- Recent images or images still under processing = SSD or fast disk in a RAID 0 configuration, where performance is number one
- Move finalized images to a long term archive location such as a RAID1 array, where performance is second to data safety.

In relation to the specific C1 catalog file itself: It is a relational database wich contains a reference to the images (regardless of how you use C1), similar to LR but with a simpler structure. Managing hundred of thousands of records should not cause any trouble with most modern computers.

James R

  • Sr. Member
  • ****
  • Offline Offline
  • Posts: 364
Re: Recommendation on Catalog Capacity
« Reply #2 on: January 08, 2016, 09:11:40 pm »

Thanks.  I'm using reference imaged database. 
Logged
Pages: [1]   Go Up