LR4 should keep raw data and processed data in memory to help responsiveness

  • 1
  • Question
  • Updated 7 years ago
I'm usually jumping between photos in LR and sometimes I scan negatives into large contact sheets and instead of cutting that up into multiple files I just create as many virtual copies in LR and crop each one to a different image. I've noticed that even with virtual copies, it takes LR 30+ seconds to switch from one virtual copy to another even though they reference the same file. Why can't it just keep the last few images(both raw data and processed pixels) in memory if there is memory to be spared. I have 8Gb installed and I'm running the 64bit version with plenty of memory to spare so I think LRs threshold for releasing memory should be a bit more conservative or user controllable.
Photo of Shao Zhang

Shao Zhang

  • 4 Posts
  • 0 Reply Likes

Posted 7 years ago

  • 1
Photo of awm

awm

  • 15 Posts
  • 0 Reply Likes
I have a couple of 20+ virtual copies of 40MB files. I just tried it and although it takes a second or two to switch, it doesn't take 30 seconds. I have a large database too. Windows 7, 64-bit, LR 4RC2 is what tried it on.
Photo of Shao Zhang

Shao Zhang

  • 4 Posts
  • 0 Reply Likes
Well the files I'm dealing with are 200-500mb scans of negatives. The may be even heavier in the future. Still, the crops are pretty small. Perhaps LR is trying to process the whole image first and then do the crop which is a bit wasteful of both CPU time and memory to store the processed data.

Indeed the responsiveness is faster with 10-40mb raw files but not everything I run through LR are those kinds of files. I sometimes run CGI renders through LR to do final color correction and those files can also be pretty big compared to a camera raw file.
Photo of jdv

jdv, Champion

  • 728 Posts
  • 56 Reply Likes
Yeah, I think you need to solve the problem you seem to be having, and let modern OS design handle the boring memory stuff.