Lightroom Classic: Import is slow after updating

  • 29
  • Problem
  • Updated 1 year ago
  • In Progress
  • (Edited)
Importing in LIghtroom is  Painfully slow in Classic.  After I upgraded to Classic I am seeing importing going from 2-3 minutes to 10-20 minutes.

Sometimes it takes 5 minutes for anything to start importing. 

This is now not a professional option with this decrease in importing speed.
Photo of Jared Cruce

Jared Cruce

  • 1 Post
  • 0 Reply Likes
  • frustrated

Posted 2 years ago

  • 29
Photo of Deborah Albert

Deborah Albert

  • 29 Posts
  • 7 Reply Likes

Nothing seems to be working in LR classic. I am looking for alternative software!


Photo of David Martin

David Martin

  • 16 Posts
  • 11 Reply Likes
Yep.  After the October 2015 "upgrade" debacle. I accept anything Adobe tells me (seels me) with a bag of salt, and never accept the upgrade unless and until the uncountable bugs have been worked out by you beta-testers; i.e., paid users of the application.

Adobe no longer tests their software; they dump it out to paid subscribers: i.e., slaves, for t us to figure out what doesn't work.

Sorry, but I don't do that.  Neither should you.  Find out how to back up to the previous version and let this be a lesson to you: Never trust Adobe.  Never.  Ever.
Photo of Deborah Albert

Deborah Albert

  • 29 Posts
  • 7 Reply Likes
How do I go back?
Photo of Deborah Albert

Deborah Albert

  • 29 Posts
  • 7 Reply Likes
Don't want to lose the very tedious work I have done since update.....
Photo of Jeffrey Tranberry

Jeffrey Tranberry, Sr. Product Manager, Digital Imaging

  • 16672 Posts
  • 2728 Reply Likes
Official Response
Engineering is working on a fix for slow import.

If you need to rollback, instructions are here: https://helpx.adobe.com/lightroom/kb/roll-back-to-prior-update.html
Photo of Brian Wiedeke

Brian Wiedeke

  • 4 Posts
  • 1 Reply Like
This was 7 months ago. Where does this stand, as I keep my products updated and it is still unacceptably slow.
Photo of Tolga Tuncay

Tolga Tuncay

  • 2 Posts
  • 0 Reply Likes
slow import is unacceptable, especially after 7 months of official respond. Please update when import will be fixed.
Photo of Clarkyboy

Clarkyboy

  • 1 Post
  • 0 Reply Likes
An update please Adobe. You are soon to lose a customer. 
Photo of Kristin Bobb

Kristin Bobb

  • 1 Post
  • 0 Reply Likes
Me too! I have been suffering for months and am so over adobe! Please fix this!
Photo of Tolga Tuncay

Tolga Tuncay

  • 2 Posts
  • 0 Reply Likes
We had this issue at one of my studios. The fix is kinda simple. Go to file- and create a new catalog. We have so many photos at once it took time for Lightroom to process the whole catalog and import etc. Just don’t lose the previous catalog, you should be able to switch in between. Let me know if this works for you guys. Thank you.
Photo of dmeephd

dmeephd

  • 300 Posts
  • 80 Reply Likes
I think most of us with large catalogs have thought about this use of multple catalogs.  I know I have.  However, I have collected over the years a great number of Lightroom books, including those penned by Victoria, the Lightroom Queen, and I cannot recall any pundit ever recommending to go with multiple catalogs.

Even Scott Kelby in his newest tome for LR Classic CC stills recommends going with one catalog.  He knows photographers with 6 million images in their catalog.  (I have 3.48 million in mine.)  Multiple catalogs might entail keeping multiple sets of presets if the presets are kept with the catalogs.

What would be a better solution is for Adobe to switch from SQLlite to a professional relational database such as MS SQL or Oracle.  Then data and metadata like presets could be retained in their own database tables and any number of catalogs—which could be smaller and topic-specific—would be able to be loaded and unloaded quickly whilst still being able to use the presets collected in a separate db.
Photo of Victoria Bampton - Lightroom Queen

Victoria Bampton - Lightroom Queen, Champion

  • 5527 Posts
  • 2204 Reply Likes
3.48 million is getting on the chunky side, and I could see why the import could be slow as it does duplicate detection. While I usually only recommend a single catalog, there's another possibility that you could consider for this scenario is a small working catalog for the stuff you're working on right now, and then transferring into your huge archive catalog when completed. That's page 432 in my Classic book.
Photo of dmeephd

dmeephd

  • 300 Posts
  • 80 Reply Likes
Too right!  On the other hand, supposedly there are ones double that size.  I friend in Hong Kong has one that was over 4M images when we were in Iceland last year.  Who knows how large it is now as he is a prolific shooter.

I have your book, and believe me I have thought about your suggestion.  On the other hand, I never had this issue with LR6 once I moved from the MacBook Pro with a 1TB SSD and 16GB RAM to the MacPro 'trash can' with a 4TB SSD and 128GB RAM.

Everything slowed down with LR 7, and I'm not the only one with this observation—this forum is filled with this complaint.

I see that Rick Flohr has cross-referenced the thread against the bug you referenced and posited a possible fix, so the problem of the 'ghost' dngs is real.

I also see that AR is still slinging accusations around as of seven (7) minutes ago.  Does this guy know when to stop?
Photo of Victoria Bampton - Lightroom Queen

Victoria Bampton - Lightroom Queen, Champion

  • 5527 Posts
  • 2204 Reply Likes
Yeah, I've seen a 7 million. I haven't tried importing into it though.

> Does this guy know when to stop?
Historically, no. He's a very knowledgeable guy and my go-to for color management, but knowing when to give up has never been his strongest point.
Photo of dmeephd

dmeephd

  • 300 Posts
  • 80 Reply Likes
I've seen larger image databases in the medical imaging industry, but none were using LR; not even sure if LR can import DICOM images which is what that industry has standardized on.  In any event, the underlying database was always a full relational DB such as MS SQL, Oracle, or DB2.  Part of the performance issue has to be centered around Adobes' use of SQLlite.

However, this still does not explain the serious performance degradation with LR 7.  My catalog has only grown by about 20k images since moving over to LR7, but the slow import process has been present from Day One.

It is not consistent.  Some imports go so fast its like the good old days; most are very slow.  I tried with another catalog which had about 20 images in it.  The catalog came from one of the LR guru books.  Importing (after the catalog was converted to the LR7 format) was still slow.  And the dng ghosting could not be replicated, but then again, it hasn't manifested itself in my main catalog either.

LR is also a memory hog, even while idle.  Overnight or during the day it will gobble up 75GB of RAM.  Frankly, I've never seen ANY program on my MacPro (and I've got the DxO suite, the FranzisPhoto suite, and others) use that much memory!  Not even Photoshop.

What's going on here, do you think?
Photo of Victoria Bampton - Lightroom Queen

Victoria Bampton - Lightroom Queen, Champion

  • 5527 Posts
  • 2204 Reply Likes
I wish I knew David. 
Photo of dmeephd

dmeephd

  • 300 Posts
  • 80 Reply Likes
Well, if you're befuddled then we're all in the soup, aren't we?  LOL

Earlier I started up LR6 and loaded the original catalog (which I kept).  I'm importing a folder from a 20TB G-Tech Thunderbolt-connected drive which has 989 images, Sony .arw raw files and matching jpegs.  The raws are from the a7RIII and they're huge, around 65MB each.

The folder is a copy which LR7 has not seen.  The import started 20 minutes ago and...well, it just finished importing as I type and 1:1 previews are now being built.

Same hardware, same OS, same everything except the version of LR.  Based on the progress bar, I'm estimating that LR6 is at least 300% faster than LR7 for the very same import.

And let's bear in mind that the LR6 version of the catalog is 37GB, versus 26-ish for the LR7 one.

As Bugs Bunny oft times said: "It just don't add up!"
Photo of ctj71081

ctj71081

  • 14 Posts
  • 1 Reply Like
Everything slowed down with LR 7, and I'm not the only one with this observation—this forum is filled with this complaint.

Just to pile on here, I have this problem as well and have been following this thread for months (maybe right after it started). My catalog is ~15,000 DNGs, so nowhere near the volume mentioned here, and when I import a shot (usually ~50 - 100 images), I have to click "import" and then go do something else for about 20 minutes while my computer churns through the process.

I'm anxiously awaiting resolution.
Photo of Deborah Albert

Deborah Albert

  • 29 Posts
  • 7 Reply Likes
Thanks
Photo of Deborah Albert

Deborah Albert

  • 29 Posts
  • 7 Reply Likes
Will I lose all recent work?
Photo of Jeffrey Tranberry

Jeffrey Tranberry, Sr. Product Manager, Digital Imaging

  • 16586 Posts
  • 2696 Reply Likes
Catalogs aren't backwards compatible. So you'd be back to where you were with your prior version catalog.
Photo of Deborah Albert

Deborah Albert

  • 29 Posts
  • 7 Reply Likes
That is what I thought. So as to not lose work and still be able to process new photos, I am looking for a good alternative to LR
Photo of Shai Ben-Naphtali

Shai Ben-Naphtali

  • 3 Posts
  • 0 Reply Likes
Deborah, I can totally feel your pain... I think that Capture One is a good candidate.
Photo of holly strauss

holly strauss

  • 2 Posts
  • 0 Reply Likes
Alien skin Exposure 3 is also good
Photo of Shai Ben-Naphtali

Shai Ben-Naphtali

  • 3 Posts
  • 0 Reply Likes
But who would want to break free from the Adobe CC total package just to pay for another software? We're already paying for one, now pay for two?
Photo of Michael Hach

Michael Hach

  • 2 Posts
  • 1 Reply Like
I've bought into ON1 Photo RAW and find it quite good. It's only two years old but the support is great, unlike Adobe who like to direct you to the FAQ or Forums pages rather than putting some one on your problem using Live chat.

Also, DxO plug-in has stopping importing back into LR since the latest LR update and the developers at DxO cant figure out why that's happening. ON1 plug-in works fine , though.
Photo of PAUL U

PAUL U

  • 14 Posts
  • 2 Reply Likes
Agreed! Adobe is dropped the ball. Its quite obvious they care little for their customers.
Photo of Boaz Yoffe

Boaz Yoffe

  • 16 Posts
  • 1 Reply Like
Deborah, please check the preview generation, it should be on embedded, this will speed up things.
Photo of Deborah Albert

Deborah Albert

  • 29 Posts
  • 7 Reply Likes
I am mostly having trouble with Develop module and LR not responding, making any work almost impossible
Photo of Boaz Yoffe

Boaz Yoffe

  • 16 Posts
  • 1 Reply Like
Please review the display card driver and turn off graphics card acceleration, it never seems to work anyway, Sorry JT
Photo of Deborah Albert

Deborah Albert

  • 29 Posts
  • 7 Reply Likes
Did that already
Photo of Petter Bäcklund

Petter Bäcklund

  • 1 Post
  • 2 Reply Likes
Still no solution for this? 

Classic CC is the worst piece of software I've ever used - why was it even released when everything is so slow compared to previous versions. I need an upgrade urgently. 
Photo of Sumeet Choudhury

Sumeet Choudhury, Employee

  • 55 Posts
  • 20 Reply Likes
Kindly install the latest update to Lightroom i.e Lightroom Classic CC 7.2. 
This should resolve your problem of Import. Kindly let us know your feedback on it.
Photo of Richard Stead

Richard Stead

  • 2 Posts
  • 6 Reply Likes
No it does not. My computer is top end, my graphics card is top end and all of a sudden importing images has become a nightmare. Do I really need to find  a full day to import 400 Raw images and concert them???
Photo of Gary Eason

Gary Eason

  • 20 Posts
  • 11 Reply Likes
Richard is right. The latest version is a basket case. Workflow crippled here too, like so many others. The only thing it has speeded up is nervous breakdowns.
Photo of PAUL U

PAUL U

  • 14 Posts
  • 2 Reply Likes
7.2 is as horrible as the last version. I'd like a refund from Adobe until the product they charge us for actually works.
Photo of Gary Eason

Gary Eason

  • 20 Posts
  • 11 Reply Likes
Update on my comment. I fixed all the issues by resetting the LR Preferences. It now flies along faster than ever. Worth a try. Astonishing that this isn't built in to the update process, given all the problems.
Photo of PAUL U

PAUL U

  • 14 Posts
  • 2 Reply Likes
I'll try that too. I'll let you know if it works.
Photo of Peter Filias

Peter Filias

  • 11 Posts
  • 3 Reply Likes
Mine was a fresh install, but it did find my old LR 3 catalog. Does that mean it had old LR settings?
Photo of JeffB

JeffB

  • 11 Posts
  • 4 Reply Likes
Speed of import both from memory cards and during folder sync is markedly improved using last update 7.2.  Thank you for correcting this issue.
Photo of Sumeet Choudhury

Sumeet Choudhury, Employee

  • 55 Posts
  • 20 Reply Likes
Happy to know that Jeff. Thanks for the appreciation !
Photo of Mike Vraneza

Mike Vraneza

  • 7 Posts
  • 4 Reply Likes
version 7.2 complete broke Lightroom on my computer.  Not only is importing exponentially slower, it freezes the program and trying to quit it to restart took 3 minutes.  Specs attached, not shown is the 3 SSDs and 1 HHD all connected via thunderbolt 2 connections.  I'm going back the last version.  SOOOOO tired of being an unpaid beta tester for Adobe....
Photo of Jeffrey Tranberry

Jeffrey Tranberry, Sr. Product Manager, Digital Imaging

  • 16586 Posts
  • 2696 Reply Likes
I'm not hearing widespread reports of this behavior. Might be a system specific. What troubleshooting steps have you tried?
Photo of Richard Stead

Richard Stead

  • 2 Posts
  • 6 Reply Likes
I have exactly the same issue. Uploading from memory card used to be quick now it takes hours!!!
Photo of scottevest

scottevest

  • 2 Posts
  • 3 Reply Likes
same here!
Photo of Hannes Svardal

Hannes Svardal

  • 4 Posts
  • 3 Reply Likes
Same here. Extremely slow after upgrade. I am on Verions 7.2.
Photo of PAUL U

PAUL U

  • 14 Posts
  • 2 Reply Likes
Adobe is obviously not interested in the pro market. I've waited for them to fix this mess they created. Its time to shop for something professional that can be relied upon.
Photo of Hannes Svardal

Hannes Svardal

  • 4 Posts
  • 3 Reply Likes
In my case they actually contacted me per email to look into the issue. We found out that it is related to reading from the memory card. When first copying the photos to the hard disk and importing from there, the problem does not occur for me. Not ideal, but a viable workaround.
Photo of scottevest

scottevest

  • 2 Posts
  • 3 Reply Likes
I too am having this problem. VERY slow importing, like 6 images a minute or so.  
Photo of Deborah Albert

Deborah Albert

  • 29 Posts
  • 7 Reply Likes
Mine is very slow and keeps crashing. have sent 10 reports to Adobe. No reply!
Photo of PAUL U

PAUL U

  • 14 Posts
  • 2 Reply Likes
Adobe has become just like Apple. Completely unresponsive to their customers needs.
Photo of Todd Shaner

Todd Shaner, Champion

  • 1763 Posts
  • 588 Reply Likes
What specific issues are you having and what trouble-shooting steps have you tried?

https://helpx.adobe.com/lightroom/kb/optimize-performance-lightroom.html

One step not listed at the above link is to reset the LR Preferences file as explained in my Mar. 10th post below. At least one person here has reported this fixed his LR 7.2 performance issues.

https://console.getsatisfaction.com/photoshop_family/conversations/import-lightroom-cc-classic-is-sl...
Photo of PAUL U

PAUL U

  • 14 Posts
  • 2 Reply Likes
Hi Todd- Just saw this note. I have tried updating, discarding preferences, installing older versions of Lightroom and have had limited success. I read the latest update fixed the issues, so I took the leap and updated to the current version (7.2). It was horrible. I just tried updating my Mac OS from El Capitan (10.11) to High Sierra (10.13). Ive had no luck whatsoever. I will try updating again to the newest Lightroom update AND delete preferences yet again. Thanks for trying to help. I'll let you know how things turn out.
Photo of Todd Shaner

Todd Shaner, Champion

  • 1763 Posts
  • 588 Reply Likes
Paul the current version is 7.3, but it has other issues–I suggest staying with 7.2 until they are resolved. If you haven't already done so create a new blank catalog and try importing about 100 image files. Let us know the results and we can try a few other suggestions.
Photo of PAUL U

PAUL U

  • 14 Posts
  • 2 Reply Likes
I'll give it a shot later this evening. Thank  you for your interest and help. This has been brutal.
Photo of PAUL U

PAUL U

  • 14 Posts
  • 2 Reply Likes
Todd - I have followed your suggestions to the "T". I downloaded version 7.2 and deleted all preferences from my library. It took 20 minutes to download 100 photos. It is certainly better than what I was experiencing. What are your thoughts?
Photo of Todd Shaner

Todd Shaner, Champion

  • 1763 Posts
  • 588 Reply Likes
Paul that's about 12 sec. per image file. On my Windows 7 system using LR 7.2 with 21 mp CR2 files 1:1 Preview building on import takes 5 sec per image file and 2 sec. for Standard previews. If I use 'Embedded & Sidecar' Import Preview selection it only takes 1 sec. per image file. Try all three Import selections and post the times so we can determine what's causing the issue. Forgot to add please provide your system specs, monitor model, camera model, and file type you're importing. Thanks!
(Edited)
Photo of Peter Filias

Peter Filias

  • 11 Posts
  • 3 Reply Likes
If you're only importing JPGs, you can keep the File Handling set to Minimal. I'd imagine that is faster?

As a test, I'm importing 9000 JPGs with Embedded & Sidecar enabled, just to see how it feels in terms of speed.
Photo of PAUL U

PAUL U

  • 14 Posts
  • 2 Reply Likes
Todd, thank you so much. The info you're providing here is invaluable! I'll shoot a bunch of pics tonight and do as you suggested. Btw, the photos I downloaded last night were from my D800 which are 36.3-megapixel in size.
(Edited)
Photo of Todd Shaner

Todd Shaner, Champion

  • 1763 Posts
  • 588 Reply Likes
You can use the same new catalog and camera files by selecting all image files in the Library Grid View and hitting the Delete key. Select 'Remove' and NOT 'Delete.' Change the Import module File Handling> Build Previews to the next of three settings (1:1, Standard, Embedded & Sidecar) and reimport the same 100 image files. Record the time and then repeat the same process for the remaining Preview selection. It will be interesting to see the differences in the three Import times.

The 36.3 megapixel D800 import times should about 1.5 to 2.0 times longer than my 21 megapixel files dependent on CPU and disk speeds compared to mine. That's of course if everything is working "normally"
(Edited)
Photo of PAUL U

PAUL U

  • 14 Posts
  • 2 Reply Likes
Okay Todd, Here you go: 
 
Importing 347 images:  RAW & JPEG (D800 @ 36.3mp each)

- Embedded & Sidecar  4min 30 sec
- Standard  4 min 43 sec
- 1:1  4 min. 49 sec.

Lightroom 7.2
Mac OS High Sierra 10.13.4 
Photo of Todd Shaner

Todd Shaner, Champion

  • 1763 Posts
  • 588 Reply Likes
Previously you said, "It took 20 minutes to download 100 photos (12 sec/file)." Now you can import 346 images in 4 min 30 sec (<1 sec/file)? From these results you must be a happy camper yes, no, confused? There should also be differences between the three types of previews selected in the Import module.

Photo of PAUL U

PAUL U

  • 14 Posts
  • 2 Reply Likes
Todd - Believe me I am confused! The differences between Embedded..., Standard, and 1:1 didn't seem like much. Each time I imported it was into a new catalog. Normally I do a lot on concert photography. I shoot thousands of photos per event. The time it was takoing made life impossible. What I need to do next is import into my regular Lightroom catalog. Does the size of the existing catalog matter? I have 350,000 photos in it currently.
Photo of PAUL U

PAUL U

  • 14 Posts
  • 2 Reply Likes
One other thing...thank you! I am hesitant to get too excited just yet. I need to see this work with my full catalog.
Photo of Todd Shaner

Todd Shaner, Champion

  • 1763 Posts
  • 588 Reply Likes
Paul, 350,000 photos in the LR catalog should not be an issue. Since you are getting good import times with a new catalog here's what I suggest you try next. Backup the current catalog if you haven't done so already. Create another new empty catalog in a separate new folder. Give it a unique name. Next go to menu File> select 'Import from Another Catalog,' select your current LR.lrcat catalog file, and check the option 'Add New Photos To CatalogWithout Moving.' It will take some time to import the catalog with 350,000 images so you may want to let it run over night. Once completed try importing files into the new merged catalog and see if this fixes the long import time.
Photo of Reetesh Mukul

Reetesh Mukul, Employee

  • 49 Posts
  • 10 Reply Likes
@Deborah Albert, @scottvest -- Please provide more details. Like what is your card spec (its speed). What is the size of image you are trying to import. Also can you provide crash report. When you are importing, what preview option you have tried. 
Photo of JeffB

JeffB

  • 11 Posts
  • 4 Reply Likes
The slow import problem has returned to my Windows 10 system.  Since the issue went away after the 7.2 update and no further changes have been made to Lightroom (as far as I know) I must assume the issue is related to some property or setting locally.  I just changed my import presets to incorporate the camera serial number into the file renaming.  My theory is that reading this metadata is taking a very long time.  I can see the new photo files being copied to my destination folders and being renamed.  The copy and renaming has been running for over an hour yet the Lightroom application still shows zero on its progress bar and displays "importing files...".

Is there any way to enable more verbose logging for Lightroom?  That would help to isolate the step that is taking the most time to complete.
Photo of Todd Shaner

Todd Shaner, Champion

  • 1766 Posts
  • 588 Reply Likes
It's possible the LR Preferences file has become corrupted, which can cause many "unexplained" issues. Try resetting as outlined at the below link. I would also suggest restarting your system if you haven't  already done so.

https://www.lightroomqueen.com/how-do-i-reset-lightrooms-preferences/
Photo of Gary Eason

Gary Eason

  • 20 Posts
  • 11 Reply Likes
Thank you, thank you, thank you. My life is redeemed. LR had become so sluggish after the latest 'update' that it had destroyed my workflow and reduced me almost to tears. Everything was painfully slow, if it worked at all. Resetting the Preferences using the simple startup method has transformed it. Faster than ever. So fast I'm feeling giddy, clicking on folders and watching the thumbnails fill the screen in an instant - instead of (say) two minutes. Hurray! Why the heck don't Adobe just incorporate this non-destructively into their Updater? 
Photo of Todd Shaner

Todd Shaner, Champion

  • 1766 Posts
  • 588 Reply Likes
Good to hear it fixed your performance issues! Every LR update that adds or changes a specific feature needs to be added or changed in your current LR Preferences file during the update process. It appears in some cases this can corrupt the file causing many different unexplained issues. The Preferences file can be corrupted in other ways such as a LR crash, memory issues, or system drive issues. It's a "dynamic" file that is constantly changing and being rewritten. That's why it's always a good idea to try resetting it as one of the first LR troubleshooting steps. It's a bit of a PITA because you'll need to manually enter custom Preference settings and reload any plugins you're using. I keep a Word doc with screenshots of the Preferences settings panels and Plugin Manager to make it easier to restore.
Photo of JeffB

JeffB

  • 11 Posts
  • 4 Reply Likes
After the last Lightroom 7.3 update the slow performance has returned and is now worse than with 7.1.  As no one from Adobe has responded to my request to provide access to logging details on the import process, I have done it myself.  One major problem I have found is that Lightroom is writing temp files to the network storage location where my images are ultimately stored.  THIS MUST STOP!  This is the worst possible performance hit.  Temp files can and should be written to fast local storage.  You need to provide a way to configure this so I can choose a local temp work path rather than forcing Lightroom to do unnecessary read / write ops across the network.

It took Lightroom 7.3 exactly 60 minutes to import 72 images into my catalog.  Total size of import was 4.2GB.  72 raf and 72 jpg sidecars.  This is absurd and no longer tenable.  I am now testing other image management systems to replace Lightroom.
Photo of dmeephd

dmeephd

  • 300 Posts
  • 80 Reply Likes
I am using Lghtroom CC 2015.14 as I refused to upgrade to Lightroom Classic CC given all of its bugs and performance issues.  I run LR on a Mac Pro 6.1 with a 3.5GHz 6-core Intel processor with 128GB of RAM—that's right...128GB!

An import of one photo shoot with raw files and jpgs, some 1400 files, takes 4 to 5 hours, not counting the preview build times.  That's obscene.  LR is no longer a useable nor viable program for professionals.
Photo of Peter Filias

Peter Filias

  • 11 Posts
  • 3 Reply Likes
For my amateur photo hobby, I had NO issues with Picasa for bulk photo importing. I wonder why I ever abandoned that. :(
Photo of Victoria Bampton - Lightroom Queen

Victoria Bampton - Lightroom Queen, Champion

  • 5527 Posts
  • 2204 Reply Likes
dmeephd, I agreed, that's crazy. So is refusing to upgrade to the latest versions, when the engineers have been working hard to solve such problems. They're not going to listen when you're using a version released months ago. Update A COPY of your catalog (actually, the upgrade would do a copy anyway!) and see if you still have the same issues. If you do, supply further information. They can't fix it if they don't know what problems you're seeing. That's not normal.
Photo of dmeephd

dmeephd

  • 300 Posts
  • 80 Reply Likes
Sorry, Victoria, but with so many reported bugs in LR Classic, including continued poor performance, one would have to either be crazy, an unecessary risk-taker, or an Adobe shill to take the plunge, change their database, and find the same old problems plus a plethoria of new ones—as have been reported in this forum and many others since the releas of LR Classic CC and LR CC.

The updating of the catalog is especially problematic.  We have read far too many reports of hours running into days to perform the update of the catalog, with the result of broken presets, hashed keywords, and missing images.  My catalog is over 30GB with just shy of 3M images, going back to film images electronically scanned from my Formula 1 days as a working pro.

I have working assignments, sometimes up to 17 days in duration, where I could shoot 1,200 images per day.   I simply cannot afford to be sidelined whilst LR makes a hash of everything I worked for for years.  Especially when Adobe NEVER responds to bug reports and their telephone customer support is anything but supportive.  It's a joke, but no one except Adobe and their bankers are laughing.
Photo of Mike Vraneza

Mike Vraneza

  • 7 Posts
  • 4 Reply Likes
I'm so tired of being abandoned by Adobe. We working professionals made them what they are, now they are clearly chasing ametuers in hopes of even higher record profits. Someone needs to come along and eat their lunch. What a joke indeed
Photo of Peter Filias

Peter Filias

  • 11 Posts
  • 3 Reply Likes
I am using Lightroom CC Classic 7.3 on a PC with an i7-6700K @4.5GHZ and16GB RAM. I am importing from a Hard Drive > Lightroom LIbrary and it is SUPER DUPER SLOW, eventually stalling, causing me to kill the process.
Photo of PAUL U

PAUL U

  • 14 Posts
  • 2 Reply Likes
I spoke with an Adobe Reprenentative yesterday who naturally knew nothing about any of these issues. I've written this before & will do so once more. Adobe has become very similar to Apple. They screw things up and rarely if ever even acknowledge their failures. Eventually - maybe months later, they find a fix and then quietly announce their update. Its a shame we've all invested so much time & money in companies like these.
Photo of Victoria Bampton - Lightroom Queen

Victoria Bampton - Lightroom Queen, Champion

  • 5511 Posts
  • 2195 Reply Likes
Hi Paul, I know it's frustrating when you have a problem and no one seems to be listening. The Adobe Reps on customer support rarely seem to know the very latest - they're trained in general support - so here is the best location for the very latest. But reading back through your posts, I can't even figure out which OS you're on, let alone exactly what problems you're seeing. In 4 months, only 12 people have "me too'd" this problem, so more information will be needed for the engineers to identify why you're having issues.
Photo of Peter Filias

Peter Filias

  • 11 Posts
  • 3 Reply Likes
Well, I'm a brand new paid user of Creative Cloud. I used to use Lightroom, years ago, when it was thinner and faster. This makes me not want to pay for Creative Cloud if my very first foray into it is slow performance.

And I forgot, there is no more Picase - just Google Photos... I could *shudder* use Windows 10 Photos app!
Photo of Victoria Bampton - Lightroom Queen

Victoria Bampton - Lightroom Queen, Champion

  • 5511 Posts
  • 2195 Reply Likes
Hi Peter. So tell us details.... From Help menu > System Info for a start, then what are you finding slow?
Photo of Peter Filias

Peter Filias

  • 11 Posts
  • 3 Reply Likes
Lightroom Classic version: 7.3 [ 1164630 ]
License: Creative Cloud
Language setting: en
Operating system: Windows 10 - Business Edition
Version: 10.0.16299
Application architecture: x64
System architecture: x64
Logical processor count: 8
Processor speed: 4.0 GHz
Built-in memory: 16323.2 MB
Real memory available to Lightroom: 16323.2 MB
Real memory used by Lightroom: 1490.3 MB (9.1%)
Virtual memory used by Lightroom: 6455.5 MB
GDI objects count: 868
USER objects count: 2017
Process handles count: 2952
Memory cache size: 0.0MB
Internal Camera Raw revision: 933
Maximum thread count used by Camera Raw: 5
Camera Raw SIMD optimization: SSE2,AVX,AVX2
Camera Raw virtual memory: 357MB / 8161MB (4%)
Camera Raw real memory: 358MB / 16323MB (2%)
System DPI setting: 120 DPI
Desktop composition enabled: Yes
Displays: 1) 3840x2160
Input types: Multitouch: No, Integrated touch: No, Integrated pen: No, External touch: No, External pen: No, Keyboard: No
Graphics Processor Info: 
DirectX: NVIDIA GeForce GTX 970 (23.21.13.9101)


Application folder: C:\Program Files\Adobe\Adobe Lightroom Classic CC
Library Path: G:\Photos\LightroomCC\LightroomCC.lrcat
Settings Folder: C:\Users\peter\AppData\Roaming\Adobe\Lightroom
Installed Plugins: 
1) AdobeStock
2) Canon Tether Plugin
3) Facebook
4) Flickr
5) LogiOptions
6) Nikon Tether Plugin
Config.lua flags: None
Adapter #1: Vendor : 10de
Device : 13c2
Subsystem : 85081043
Revision : a1
Video Memory : 4043
Adapter #2: Vendor : 1414
Device : 8c
Subsystem : 0
Revision : 0
Video Memory : 0
AudioDeviceIOBlockSize: 1024
AudioDeviceName: Speakers (Realtek High Definition Audio)
AudioDeviceNumberOfChannels: 2
AudioDeviceSampleRate: 48000
Build: Uninitialized
Direct2DEnabled: false
GL_ACCUM_ALPHA_BITS: 16
GL_ACCUM_BLUE_BITS: 16
GL_ACCUM_GREEN_BITS: 16
GL_ACCUM_RED_BITS: 16
GL_ALPHA_BITS: 0
GL_BLUE_BITS: 8
GL_DEPTH_BITS: 24
GL_GREEN_BITS: 8
GL_MAX_3D_TEXTURE_SIZE: 2048
GL_MAX_TEXTURE_SIZE: 16384
GL_MAX_TEXTURE_UNITS: 4
GL_MAX_VIEWPORT_DIMS: 16384,16384
GL_RED_BITS: 8
GL_RENDERER: GeForce GTX 970/PCIe/SSE2
GL_SHADING_LANGUAGE_VERSION: 4.60 NVIDIA
GL_STENCIL_BITS: 8
GL_VENDOR: NVIDIA Corporation
GL_VERSION: 4.6.0 NVIDIA 391.01
GPUDeviceEnabled: false
OGLEnabled: true
GL_EXTENSIONS: GL_AMD_multi_draw_indirect GL_AMD_seamless_cubemap_per_texture GL_AMD_vertex_shader_viewport_index GL_AMD_vertex_shader_layer GL_ARB_arrays_of_arrays GL_ARB_base_instance GL_ARB_bindless_texture GL_ARB_blend_func_extended GL_ARB_buffer_storage GL_ARB_clear_buffer_object GL_ARB_clear_texture GL_ARB_clip_control GL_ARB_color_buffer_float GL_ARB_compatibility GL_ARB_compressed_texture_pixel_storage GL_ARB_conservative_depth GL_ARB_compute_shader GL_ARB_compute_variable_group_size GL_ARB_conditional_render_inverted GL_ARB_copy_buffer GL_ARB_copy_image GL_ARB_cull_distance GL_ARB_debug_output GL_ARB_depth_buffer_float GL_ARB_depth_clamp GL_ARB_depth_texture GL_ARB_derivative_control GL_ARB_direct_state_access GL_ARB_draw_buffers GL_ARB_draw_buffers_blend GL_ARB_draw_indirect GL_ARB_draw_elements_base_vertex GL_ARB_draw_instanced GL_ARB_enhanced_layouts GL_ARB_ES2_compatibility GL_ARB_ES3_compatibility GL_ARB_ES3_1_compatibility GL_ARB_ES3_2_compatibility GL_ARB_explicit_attrib_location GL_ARB_explicit_uniform_location GL_ARB_fragment_coord_conventions GL_ARB_fragment_layer_viewport GL_ARB_fragment_program GL_ARB_fragment_program_shadow GL_ARB_fragment_shader GL_ARB_fragment_shader_interlock GL_ARB_framebuffer_no_attachments GL_ARB_framebuffer_object GL_ARB_framebuffer_sRGB GL_ARB_geometry_shader4 GL_ARB_get_program_binary GL_ARB_get_texture_sub_image GL_ARB_gl_spirv GL_ARB_gpu_shader5 GL_ARB_gpu_shader_fp64 GL_ARB_gpu_shader_int64 GL_ARB_half_float_pixel GL_ARB_half_float_vertex GL_ARB_imaging GL_ARB_indirect_parameters GL_ARB_instanced_arrays GL_ARB_internalformat_query GL_ARB_internalformat_query2 GL_ARB_invalidate_subdata GL_ARB_map_buffer_alignment GL_ARB_map_buffer_range GL_ARB_multi_bind GL_ARB_multi_draw_indirect GL_ARB_multisample GL_ARB_multitexture GL_ARB_occlusion_query GL_ARB_occlusion_query2 GL_ARB_parallel_shader_compile GL_ARB_pipeline_statistics_query GL_ARB_pixel_buffer_object GL_ARB_point_parameters GL_ARB_point_sprite GL_ARB_polygon_offset_clamp GL_ARB_post_depth_coverage GL_ARB_program_interface_query GL_ARB_provoking_vertex GL_ARB_query_buffer_object GL_ARB_robust_buffer_access_behavior GL_ARB_robustness GL_ARB_sample_locations GL_ARB_sample_shading GL_ARB_sampler_objects GL_ARB_seamless_cube_map GL_ARB_seamless_cubemap_per_texture GL_ARB_separate_shader_objects GL_ARB_shader_atomic_counter_ops GL_ARB_shader_atomic_counters GL_ARB_shader_ballot GL_ARB_shader_bit_encoding GL_ARB_shader_clock GL_ARB_shader_draw_parameters GL_ARB_shader_group_vote GL_ARB_shader_image_load_store GL_ARB_shader_image_size GL_ARB_shader_objects GL_ARB_shader_precision GL_ARB_shader_storage_buffer_object GL_ARB_shader_subroutine GL_ARB_shader_texture_image_samples GL_ARB_shader_texture_lod GL_ARB_shading_language_100 GL_ARB_shader_viewport_layer_array GL_ARB_shading_language_420pack GL_ARB_shading_language_include GL_ARB_shading_language_packing GL_ARB_shadow GL_ARB_sparse_buffer GL_ARB_sparse_texture GL_ARB_sparse_texture2 GL_ARB_sparse_texture_clamp GL_ARB_spirv_extensions GL_ARB_stencil_texturing GL_ARB_sync GL_ARB_tessellation_shader GL_ARB_texture_barrier GL_ARB_texture_border_clamp GL_ARB_texture_buffer_object GL_ARB_texture_buffer_object_rgb32 GL_ARB_texture_buffer_range GL_ARB_texture_compression GL_ARB_texture_compression_bptc GL_ARB_texture_compression_rgtc GL_ARB_texture_cube_map GL_ARB_texture_cube_map_array GL_ARB_texture_env_add GL_ARB_texture_env_combine GL_ARB_texture_env_crossbar GL_ARB_texture_env_dot3 GL_ARB_texture_filter_anisotropic GL_ARB_texture_filter_minmax GL_ARB_texture_float GL_ARB_texture_gather GL_ARB_texture_mirror_clamp_to_edge GL_ARB_texture_mirrored_repeat GL_ARB_texture_multisample GL_ARB_texture_non_power_of_two GL_ARB_texture_query_levels GL_ARB_texture_query_lod GL_ARB_texture_rectangle GL_ARB_texture_rg GL_ARB_texture_rgb10_a2ui GL_ARB_texture_stencil8 GL_ARB_texture_storage GL_ARB_texture_storage_multisample GL_ARB_texture_swizzle GL_ARB_texture_view GL_ARB_timer_query GL_ARB_transform_feedback2 GL_ARB_transform_feedback3 GL_ARB_transform_feedback_instanced GL_ARB_transform_feedback_overflow_query GL_ARB_transpose_matrix GL_ARB_uniform_buffer_object GL_ARB_vertex_array_bgra GL_ARB_vertex_array_object GL_ARB_vertex_attrib_64bit GL_ARB_vertex_attrib_binding GL_ARB_vertex_buffer_object GL_ARB_vertex_program GL_ARB_vertex_shader GL_ARB_vertex_type_10f_11f_11f_rev GL_ARB_vertex_type_2_10_10_10_rev GL_ARB_viewport_array GL_ARB_window_pos GL_ATI_draw_buffers GL_ATI_texture_float GL_ATI_texture_mirror_once GL_S3_s3tc GL_EXT_texture_env_add GL_EXT_abgr GL_EXT_bgra GL_EXT_bindable_uniform GL_EXT_blend_color GL_EXT_blend_equation_separate GL_EXT_blend_func_separate GL_EXT_blend_minmax GL_EXT_blend_subtract GL_EXT_compiled_vertex_array GL_EXT_Cg_shader GL_EXT_depth_bounds_test GL_EXT_direct_state_access GL_EXT_draw_buffers2 GL_EXT_draw_instanced GL_EXT_draw_range_elements GL_EXT_fog_coord GL_EXT_framebuffer_blit GL_EXT_framebuffer_multisample GL_EXTX_framebuffer_mixed_formats GL_EXT_framebuffer_multisample_blit_scaled GL_EXT_framebuffer_object GL_EXT_framebuffer_sRGB GL_EXT_geometry_shader4 GL_EXT_gpu_program_parameters GL_EXT_gpu_shader4 GL_EXT_multi_draw_arrays GL_EXT_packed_depth_stencil GL_EXT_packed_float GL_EXT_packed_pixels GL_EXT_pixel_buffer_object GL_EXT_point_parameters GL_EXT_polygon_offset_clamp GL_EXT_post_depth_coverage GL_EXT_provoking_vertex GL_EXT_raster_multisample GL_EXT_rescale_normal GL_EXT_secondary_color GL_EXT_separate_shader_objects GL_EXT_separate_specular_color GL_EXT_shader_image_load_formatted GL_EXT_shader_image_load_store GL_EXT_shader_integer_mix GL_EXT_shadow_funcs GL_EXT_sparse_texture2 GL_EXT_stencil_two_side GL_EXT_stencil_wrap GL_EXT_texture3D GL_EXT_texture_array GL_EXT_texture_buffer_object GL_EXT_texture_compression_dxt1 GL_EXT_texture_compression_latc GL_EXT_texture_compression_rgtc GL_EXT_texture_compression_s3tc GL_EXT_texture_cube_map GL_EXT_texture_edge_clamp GL_EXT_texture_env_combine GL_EXT_texture_env_dot3 GL_EXT_texture_filter_anisotropic GL_EXT_texture_filter_minmax GL_EXT_texture_integer GL_EXT_texture_lod GL_EXT_texture_lod_bias GL_EXT_texture_mirror_clamp GL_EXT_texture_object GL_EXT_texture_shared_exponent GL_EXT_texture_sRGB GL_EXT_texture_sRGB_decode GL_EXT_texture_storage GL_EXT_texture_swizzle GL_EXT_timer_query GL_EXT_transform_feedback2 GL_EXT_vertex_array GL_EXT_vertex_array_bgra GL_EXT_vertex_attrib_64bit GL_EXT_window_rectangles GL_EXT_import_sync_object GL_IBM_rasterpos_clip GL_IBM_texture_mirrored_repeat GL_KHR_context_flush_control GL_KHR_debug GL_EXT_memory_object GL_EXT_memory_object_win32 GL_EXT_win32_keyed_mutex GL_KHR_parallel_shader_compile GL_KHR_no_error GL_KHR_robust_buffer_access_behavior GL_KHR_robustness GL_EXT_semaphore GL_EXT_semaphore_win32 GL_KTX_buffer_region GL_NV_alpha_to_coverage_dither_control GL_NV_bindless_multi_draw_indirect GL_NV_bindless_multi_draw_indirect_count GL_NV_bindless_texture GL_NV_blend_equation_advanced GL_NV_blend_equation_advanced_coherent GL_NV_blend_minmax_factor GL_NV_blend_square GL_NV_command_list GL_NV_compute_program5 GL_NV_conditional_render GL_NV_conservative_raster GL_NV_conservative_raster_dilate GL_NV_copy_depth_to_color GL_NV_copy_image GL_NV_depth_buffer_float GL_NV_depth_clamp GL_NV_draw_texture GL_NV_draw_vulkan_image GL_NV_ES1_1_compatibility GL_NV_ES3_1_compatibility GL_NV_explicit_multisample GL_NV_fence GL_NV_fill_rectangle GL_NV_float_buffer GL_NV_fog_distance GL_NV_fragment_coverage_to_color GL_NV_fragment_program GL_NV_fragment_program_option GL_NV_fragment_program2 GL_NV_fragment_shader_interlock GL_NV_framebuffer_mixed_samples GL_NV_framebuffer_multisample_coverage GL_NV_geometry_shader4 GL_NV_geometry_shader_passthrough GL_NV_gpu_program4 GL_NV_internalformat_sample_query GL_NV_gpu_program4_1 GL_NV_gpu_program5 GL_NV_gpu_program5_mem_extended GL_NV_gpu_program_fp64 GL_NV_gpu_shader5 GL_NV_half_float GL_NV_light_max_exponent GL_NV_multisample_coverage GL_NV_multisample_filter_hint GL_NV_occlusion_query GL_NV_packed_depth_stencil GL_NV_parameter_buffer_object GL_NV_parameter_buffer_object2 GL_NV_path_rendering GL_NV_path_rendering_shared_edge GL_NV_pixel_data_range GL_NV_point_sprite GL_NV_primitive_restart GL_NV_query_resource GL_NV_query_resource_tag GL_NV_register_combiners GL_NV_register_combiners2 GL_NV_sample_locations GL_NV_sample_mask_override_coverage GL_NV_shader_atomic_counters GL_NV_shader_atomic_float GL_NV_shader_atomic_fp16_vector GL_NV_shader_atomic_int64 GL_NV_shader_buffer_load GL_NV_shader_storage_buffer_object GL_NV_texgen_reflection GL_NV_texture_barrier GL_NV_texture_compression_vtc GL_NV_texture_env_combine4 GL_NV_texture_multisample GL_NV_texture_rectangle GL_NV_texture_rectangle_compressed GL_NV_texture_shader GL_NV_texture_shader2 GL_NV_texture_shader3 GL_NV_transform_feedback GL_NV_transform_feedback2 GL_NV_uniform_buffer_unified_memory GL_NV_vertex_array_range GL_NV_vertex_array_range2 GL_NV_vertex_attrib_integer_64bit GL_NV_vertex_buffer_unified_memory GL_NV_vertex_program GL_NV_vertex_program1_1 GL_NV_vertex_program2 GL_NV_vertex_program2_option GL_NV_vertex_program3 GL_NV_viewport_array2 GL_NV_viewport_swizzle GL_NVX_conditional_render GL_NVX_gpu_memory_info GL_NVX_multigpu_info GL_NVX_nvenc_interop GL_NV_shader_thread_group GL_NV_shader_thread_shuffle GL_KHR_blend_equation_advanced GL_KHR_blend_equation_advanced_coherent GL_SGIS_generate_mipmap GL_SGIS_texture_lod GL_SGIX_depth_texture GL_SGIX_shadow GL_SUN_slice_accum GL_WIN_swap_hint WGL_EXT_swap_control
In general, importing folders with a few thousand photos... I wanted to import ALL of my photos (100K+) but have gone year-by-year for now.
Photo of Peter Filias

Peter Filias

  • 11 Posts
  • 3 Reply Likes
I just picked my next folder, 2015, which has about 5500 photos, and it hasn't even moved past the empty-looking "Importing files..." window. 

It currently has only 701 photos imported from a previous attempt that I had to cancel because I couldn't wait all day.
Photo of dmeephd

dmeephd

  • 300 Posts
  • 80 Reply Likes
Exactly.  This behavior is not new to LR CLassic CC; it has been going on for several iterations now, and all Adobe has been doing is adding useless features and ignoring performance issues.
Photo of Peter Filias

Peter Filias

  • 11 Posts
  • 3 Reply Likes
So what's the alternative, on a PC (my main rig) or a Mac? I don't want to pay $300 for Capture One. Heck, there are probably others out there... I just haven't looked in a few years since just the other day when I purchased Adobe CC. Now I wonder...
Photo of dmeephd

dmeephd

  • 300 Posts
  • 80 Reply Likes
Many are looking at ON1 products.  Capture Pro is a bit pricey, but if it works, then it changes the equation?  My biggest hurdle is moving the database from LR to something else and not losing the keywords, the edits, and last but not least, the Smart Collections.

It's a real problem, and caused by Adobe and their inability (or refusal) to cater to the needs of the working professional and upgrade the foundation of their database from SQL Lite to a full relational database like MS SQL or Oracle.  This simple design change alone would solve most, if not all of the performance issues, but it would raise the cost—or lower the profits—of each copy sold because of increased licensing costs from the DB supplier.

Unfortunately, it appears that Adobe doesn't even bother to ask working pros if they would pay more for higher performance.  Adobe seems to be focused on the cellphone picture crowd who do not want to pay much if anything for a DAM application, and are using LR primarily on their phones of notepads.

I spent over $7k on my hardware, not including over 80TB in external drives for redundant backup.  My Mac Pro 6.1 (the trash can) has a 3.5GHz 6-core processor, a 4TB SSD drive, and 128GB of RAM (along with two video processors, each with 6GB of RAM).  It's about as high powered a Mac as one can buy, thanks to third-party vendors.  And granted, it improved LR's performance over my Macbook Pro with 16GB, but heck—it still takes 15 - 30 minutes to optimize the catalog (down from hours on the laptop).  And that is all because of the underlying database.

So saveth experts in Adobe who used to work on LR but have now moved to other products.
Photo of Peter Filias

Peter Filias

  • 11 Posts
  • 3 Reply Likes
I still cannot import my 2015 folder of 5494 pictures. No matter how many times I try, it never imports. It's still at only 701 photos.

Update: After closing Lightroom and relaunching it, it looks like it's able to start importing from that folder. My question: Why, and why is this acceptable for Adobe?
(Edited)
Photo of JeffB

JeffB

  • 11 Posts
  • 4 Reply Likes
I am migrating my studio to Capture One.  Adobe is no longer a viable option for me.  After 20 years   Adobe has abandoned me.
Photo of PAUL U

PAUL U

  • 14 Posts
  • 2 Reply Likes
I am resisting but it does appear the writing is on the wall for many of us. It appears Adobe has gotten too big to care about their customers.
Photo of Reetesh Mukul

Reetesh Mukul, Employee

  • 49 Posts
  • 10 Reply Likes
We will replicate this issue locally and find a solution for it.