Lightroom: Preload adjacent photos of the strip to save time.

  • 12
  • Idea
  • Updated 6 years ago
  • (Edited)
Even with a SSD, 16gb ROM and an i7 2600k, moving on to the next photo on a film strip results in about one second of "loading" to correctly display the next image. If the system has the resources (which aren't more than a bit of RAM and some available processor) Lightroom should preload adjacent photographs to save a little time when jumping from one photo to the next.

"It's just one second", you say? Well, take 600 pics in a strip and you'll have lost 10 minutes of your day waiting for the next picture to load up to start processing.
Photo of Rafael Lemieszek

Rafael Lemieszek

  • 4 Posts
  • 0 Reply Likes

Posted 6 years ago

  • 12
Photo of jdv

jdv, Champion

  • 728 Posts
  • 56 Reply Likes
It's probably generating previews. What happens if you go through a number of images this way, and then go back and try again? You also don't say whether you are in the Library or Develop modules. It matters.

Also, there are reports that the filmstrip might be the source of some issues. Can you reproduce paging through loupe views with no filmstrip showing?

(I made this into a Problem because there is something going on here that needs to be solved. Anyway, the idea of "preloading" previews is already being done in various views with fast-load DNG data, previews and ACR cache and so on.)
Photo of Dorin Nicolaescu-Musteață

Dorin Nicolaescu-Musteață, Champion

  • 703 Posts
  • 38 Reply Likes
I always had a feeling that Lr does that at least for one photo and at least for the next one in a sequence. And at least in Library.

I might be wrong.
Photo of Rob Cole

Rob Cole

  • 4831 Posts
  • 379 Reply Likes
Perhaps this should be a feature request instead of bug report.
Photo of Rafael Lemieszek

Rafael Lemieszek

  • 4 Posts
  • 0 Reply Likes
Hi John, and thanks for the reply!

I reported it as an idea rather than a problem because it's not exactly a problem, just a part of Lightroom. I'm not sure I explained myself well.

I'm in "Develop" module and I just finished adjusting an image. I press the "right" key to advance to the following image. A preview (quite low-res, though my catalog is set to 1440px previews - not sure it has anything to do with it) of that photograph appears instantly, but it takes LR about 1 second (on my current computer) to load it in screen resolution. The "Loading..." message persists for another second.

It's almost nothing, I know. But when I'm breezing through the ~400 or ~500 pictures taken in a day to rank and select the ones I'm working on, 400 or 500 seconds are relevant. I'm not sure how long that 1 second takes on slower machines.

I just guess it wouldn't drain too much resource if you made it so that, whatever Lightroom does when you select an image in Develop module, it already did when I'm looking at the picture right before it.

(FWIW, I'm using NEF files from a D7000.)
Photo of Rob Cole

Rob Cole

  • 4831 Posts
  • 379 Reply Likes
I think it's an excellent idea. This is exactly what I did for my web photo browsing app. Try to anticipate what the user is likely to view/edit next, and have it ready.

Obviously the next one in the filmstrip would be the most likely if user is going sequentially through them... And users who know the caching algorithm can take advantage of it on purpose (e.g. go through them sequentially).

I'd like to see them saved a bit longer too - present ram-cache is only 3-images deep.

Then if the disk could be used to save them even longer, instead of the 15% baked version saved in ACR cache, we'd really be having things.

I hope the future brings more performance improvements like this...

Rob
Photo of Rafael Lemieszek

Rafael Lemieszek

  • 4 Posts
  • 0 Reply Likes
Hi there,

Any chance we might turn this topic back into a feature request?

Thanks.
Photo of Dorin Nicolaescu-Musteață

Dorin Nicolaescu-Musteață, Champion

  • 703 Posts
  • 38 Reply Likes
Do you want Lightroom to move fast between photos or do you want to know that Lightroom is prefetching photos?

I think it's best to bring up problems here. Engineers are those who have to look for solutions.
Photo of Stefan Keller

Stefan Keller

  • 10 Posts
  • 1 Reply Like
LR4 is (mostly) slower than LR3 (on my i7-2600K, W7 64bit) but it could easily outperform LR3 using smart caching!

that means caching in RAM the images I need in the Moment!
not storing big directories on the harddisk which are not really used...

e.g. zooming in and out and in and in develop Module - without changing anything - causes:

recalculating and recalculating and recalculating and recalculating and recalculating and recalculating ...

PS does a much better job here, (and a little bit LR in loupe view!)

there could be a "magic" trick (additionally to tweaking the renderengine)

e.g. xnview loads and calculates the next Image while the user is looking at the current image, or editing it

pressing the "next" key therefore loads it immediately!
and of course zooming in and out works without delay

LR4.2, please implement this and preload/precalculate the 1:1 view and use it in develop mode,

and load also the previous image and the image after the next in advance
and some more, I have enough RAM. please use it!

Stefan

This reply was created from a merged topic originally titled
Improve LR performance with (pre-) caching.