Skip to main content
jsk09
Inspiring
December 13, 2017
Question

LR Classic high CPU Usage

  • December 13, 2017
  • 1 reply
  • 1379 views

Since updating to LR Classic, whenever I Import or Export I get a warning that Lightroom is causing high CPU usage.  I NEVER got that before upgrading. Along with that, import and export is painfully slow. I posted a note on that a few days ago. I'm running an Intel i7-6700K 4GHz Skylake processor so I know it''s not a CPU capacity issue, Adobe did something that needs to be found and fixed.

    This topic has been closed for replies.

    1 reply

    Ian Lyons
    Community Expert
    Community Expert
    December 13, 2017

    One of the performance enhancements introduced in Lr Classic was to use as many cores as possible when importing images into the catalog.

    If you're seeing slow imports then it would be important that the engineering team knows what size of preview is being built during import, and whether your converting to DNG on import. Also, helps to include details of OS and amount of installed ram

    jsk09
    jsk09Author
    Inspiring
    December 13, 2017

    Ian, Here are the details:
    System: 32gig RAM, NVidia GTX970 graphics card, Intel i7 6700-K 4Ghz CPU, 64 bit Windows 10 Pro, 512 M@ SSD for library and cache, 3tb HDD storage

    LR Details: Std Preview 1440 Pixels, Preview Quality Medium, Smart Preview total size 14 Gig, Import as .jpg

    Thanks

    Ian Lyons
    Community Expert
    Community Expert
    December 13, 2017

    Import should be super fast on your system.

    I'm not sure what you mean by import as JPG. Do you mean the originals are JPG files?

    Are the files being imported from the camera/card reader or direct from disk?

    Are you using USB 2 or 3?

    Can you try an alternative import method. That is, if you normally copy from memory card then try copying the images to disk then use 'Add' in port window.

    Also, worth checking whether stopping smart preview building during import as I recall some mention elsewhere that this wasn't working as expected in Win 10