Lightroom Classic CC - Import/Move hanging for hours...

[spikeman512]

Problem:  Decent import speed, but final step of "Move and Import Photos" has been hanging at a dead stop for over two hours (it looks like perhaps 5% would be left on status bar).  Memory is at 71% ; CPU is at 14% ; HD is almost zero usage.

I installed Lightroom Classic CC for a client this afternoon...left most of defaults such as GPU acceleration (it's an Intel card).
Importing from 250 GB of photos (41,000 qty)...imported as MOVE from original location to another folder used for Lightroom Photos.
Very fast PC.  New Dell XPS.

i7 ; 32 GB RAM; 2 TB Samsung SSD NVME drive
Importing from a folder on the SSD drive into other SSD folder...so, it should be very fast.

Import was perhaps 1 hour...only 100GB was imported (21,000 qty)...maybe 1/2 were dupes?  I can't tell yet since it hasn't finished or given any post-completion messags.

Questions: 

Any idea why it is hanging for SO long? 

Is there any way I can estimate the completion time?

Even though the photos look like they are already imported (and copied into the new proper folders), I don't want to cancel/reboot just in case there are important steps that won't finish unless I leave it alone.  In my past experience on my own computer, the MOVE option in import causes files to actually be MOVED out of source folder (so that they are no longer there), but right now, all source files are still there...thus, I am assuming it hasn't finished the move/delete process from the source.  I know LR doesn't delete from memory cards when importing, but it is supposed to delete from source when doing a move from the same hard drive.

-Shannon

Lightroom Classic version: 8.1 [ 1200465 ]

License: Creative Cloud

Language setting: en

Operating system: Windows 10 - Business Edition

Version: 10.0.17763

Application architecture: x64

System architecture: x64

Logical processor count: 12

Processor speed: 3.6 GHz

Built-in memory: 32571.2 MB

Real memory available to Lightroom: 32571.2 MB

Real memory used by Lightroom: 3872.7 MB (11.8%)

Virtual memory used by Lightroom: 17771.3 MB

GDI objects count: 746

USER objects count: 2093

Process handles count: 44453

Memory cache size: 2336.7MB

Internal Camera Raw version: 11.1 [ 112 ]

Maximum thread count used by Camera Raw: 5

Camera Raw SIMD optimization: SSE2,AVX,AVX2

Camera Raw virtual memory: 724MB / 16285MB (4%)

Camera Raw real memory: 731MB / 32571MB (2%)

System DPI setting: 96 DPI

Desktop composition enabled: Yes

Displays: 1) 1920x1080

Input types: Multitouch: No, Integrated touch: No, Integrated pen: No, External touch: No, External pen: No, Keyboard: No

Graphics Processor Info:

DirectX: Intel(R) UHD Graphics 630 (24.20.100.6290)

[GoldingD]

I you were importing, say 1000 photos, it might take a few hours. And you are importing 41,000? Yikes. That will take forever.

Now, one concern, you state in the import you are Moving. Are you moving from the SD card? or from a hard drive? If the later, are the images still on the SD card?

Never ever move your originals from the SD card, what if something goes wrong.And do not format the SD card (in camera please) until you have at least one  backup (that i on two or more locations other than the SD card, and preferably not on the same hard drive)

If you copied the images from the SD card to a hard drive, OK, but place them in the folder LR expects to find them, and then upon import just do an ADD, saves you time.

Now, I doubt you are moving 41,000 images from an SD card, even if they were JPEG's But if that was possible,(well OK, a 256 GB card is in market)  the time it would take, I would be concerned with melting that SD card from the buildup of heat (OK, melting is overstated, but that would not be healthy for the card)

I stated SD card, of course your memory card might be different.

[spikeman512]

Thanks for input.  There was no memory card involved...the photos were in a structure of disorganized folders that were indeed on the hard drive.  I know it could take awhile, but again, this is a VERY fast computer with tons of memory and a blazingly fast NVME SSD drive that reads and writes about 1,800 MB/sec.  The import was pretty fast...the question I have is "what the heck is going on during the last few percentage points of time on the progress bar after all of the photos have already been imported?"  It has taken over three hours at this dead stop...but with 70% memory usage and 15% CPU usage and almost zero hard drive usage.

A benefit of a move is that any photos that fail, will remain in the source folder...and you can handle them as needed.  If you do the ADD option, and there are problems, you cannot easily separate out the problem photos.

I broke a big cardinal rule...I should have imported a small subset first...and then progressed from there....I wasn't thinking, and did the entire group all at once.  : /

-s

[dj_paige]

I hear this problem mentioned from time to time, I don't know what causes it. Possible solution: import in smaller batches. There's no way of estimating when it will finish, or even if it will finish (seems to me like it isn't doing anything and has just hung up). It's most likely a bug of some sort.

And a side issue:

Importing from a folder on the SSD drive into other SSD folder...so, it should be very fast.

Actually speed of the disk is a trivial component of the time it should take. Most of the time is taken by the CPU generating previews.

[spikeman512]

Yep...I should have done smaller batches...and I know better.  dammit.
the preview generation process is one thing I don't know much about...in terms of how long it takes, the actual details, how to make it more efficient, etc.

i just decided...I'm going to abort it....reboot....then I'm going to re-import in batches....it should filter out the dupes...I guess I'll manually have to delete the source.

at least this way, I can make sure I don't miss any fotos....my day will be shot, but oh well....blame my OCD when it comes to this type of stuff.

-s

[joachims25232702]

If I do a simple import of 100 photos, then my Win10 system uses 4Gbyte if memory too - same as your massive import. I guess this is simply a coding problem that they do not allow allocation of more Ram and hence your system gets clogged up with a massive import. Chances are it tried to import the photos via some emergency pipeline after the allocated Ram was exhausted.

[dj_paige]

Importing does not use much RAM. It uses the CPU heavily, that is the limiting factor.

[joachims25232702]

So the import hang because the CPU was exhausted?

[dj_paige]

Importing usually hangs because of a bug.