Has anyone tried moving the cache directory to separate external drive to shrink catalog and add performance?

Hi all,

I found this interesting article, where the person had basically gone into the package where the catalog is kept on a Mac....moved the cache to an external SSD, deleted the original and then added a soft link on the OS that would point to the cache you'd just created on the external SSD and C1 would happily chug along using that cache on the soft link.

This looks to be a good example of how to not only shrink your catalog contents taking up space likely on your main hard drive, but to also add some performance by cutting down IO on your main drive...much in the same fashion as you do when using an external drive tor your images, separating them from your application on the main system drive.

Has anyone out there tried this or have a similar solution?

This seems like a no brainer for Capture One to implement as that most all other stills and video editors I've worked with have the ability in their preferences to separate out the caching from the main system drive.

Thoughts?

Experience doing something like this?

Thanks in advance,

cayenne

Nikon Shooter

5. September 2020 07:16

I work in sessions exclusively… so it is as big as the files it contains.

I leave the session folder — and its content of sidecar files and thumb-
nail — on the main drive but all the RAWs are on a peripheral memory.

If you like to work in catalogues, you may well have different ones for
say… wildlife, city, landscape, etc, to keep them at reasonable size
and increase app performance.

Kommentare