What should I put on an SSD to make Lightroom faster: catalog, previews, or cache?

Asked 6/22/2016

4 views

2 answers

0

I have Lightroom 6.6 on Windows 10. Lightroom and the OS are already installed on a 256GB Samsung 850 EVO SSD, with about 156GB free. My current Lightroom storage setup is:

  • catalog, previews, and backups on a 2TB hard drive
  • cache on the 2TB hard drive
  • photo files stored separately

For a system with this kind of hardware, what Lightroom files benefit most from being on the SSD?

Would it make sense to move the catalog and previews to the SSD and keep only backups on the HDD? Should the Camera Raw/cache also be on the SSD, and if so, does cache size matter much? I’m mainly interested in changes that are actually noticeable in day-to-day use, not just benchmark differences.

Originally by Photography Stack Exchange contributor. Source · Licensed CC BY-SA 4.0

Photography Stack Exchange contributor

10y ago

2 Answers

0

Your machine is pretty adequate in terms of processing power (unless you shoot in medium format). 8Gb of RAM should also be quite enough if you don't run another heavy app in parallel.

Depending on the size of your catalog you may or may not notice a big difference when moving around catalog and cache. But, since Lightroom catalog is comprised of lots of small files and folders (in total about twice as there are images), there can be a noticeable improvement using SSD. This is due to faster file system access coming from less latency and no fragmentation effect which might be there for HDD.

Anyway, I just did a test of having a catalog of about 40K items located on HDD versus SSD. The images themselves are on another drive so their location is not a factor.

While having the catalog and cache on HDD (RAID1 of 2x7200rpm), ready time of Lightroom (when all of the imported folders display their number of items) is about 3 minutes. This is on cold start. When restarting Lightroom, it is ready almost instantly which is an effect of available RAM.

When the catalog and cache are on SSD, the cold start time is maybe 2 seconds.

So, placing your catalog and cache on the SSD would be the best way to improve cold start performance. Since your previews only take 10Gb, I'd say it is not critical to limit the cache storage size yet.

The effect of limiting the cache size is that the least recently accessed items get deleted when newly accessed items needs to be cached. That's fine if you mostly look at the same or new images, but if you browse more randomly, limited cache will not do much for improving the performance.

Tangentially, having more RAM would make it easier to browse back and forth while having more processing power would make it (slightly) faster to import new images and do the processing.

Originally by user53303. Source · Licensed CC BY-SA 4.0

user53303

10y ago

0

AI Answer

Generated from our catalog & community — verify before relying on it.

The biggest SSD win in Lightroom is usually the catalog and cache, not the application install itself. Lightroom’s catalog/previews involve lots of small file reads and writes, and SSDs help there because access latency is much lower than with a hard drive.

Based on the answers, a good setup is:

  • put the catalog on the SSD
  • put previews on the SSD if space allows
  • put the Lightroom/Camera Raw cache on the SSD
  • keep backups on the HDD
  • image files can stay on the HDD or another drive

This can make Library tasks feel more responsive, especially browsing, loading previews, and general catalog navigation. Whether the improvement is dramatic depends on catalog size, but it can be noticeable.

The Develop module is often limited more by CPU/RAM and preview generation than by disk speed alone, so don’t expect SSD storage to transform every operation equally.

With plenty of free SSD space, moving the catalog and cache there is a sensible first step. If your previews are only around 10GB, keeping them on the SSD is also reasonable. Cache size matters less than putting it on fast storage.

UniqueBot

AI

10y ago

Your Answer