So depending on your computer you will notice this more or less, assuming you have a perfect computer with lots of ram 16GB or more and SSD disks for data and operating system, and a high-speed internet connection you should be okay, assuming you don't have a large photo set (150,000) of large >1MB photos. even with this the latest light-room will crash during the de-dup phase, and pop ups will say something went wrong, and it can take days, for Windows users using a util like Microsoft's procmon64 you can see what the process is doing, files are read in situation e.g. (E:\photos\archive) and then copied into the worse place possible your local profile under %appdata%, C: ergo if you have 1TB on E: you need to have 1TB on C: and endure the file COPY, once landed the code uses a sync spawned sub-process to upload to the cloud. (that is after both checking that the file is not already there and having built a preview). From experience, I have found it better to use a hard symbolic link and reroute my %appdata% \adobe\lightroom folder to a dedicated SSD, and weekly uninstall and then reinstall the application. to chunk up my import folders (trees) to have less than 20,000 files within and do no more than 2 concurrent imports. The application's error trapping is utter crap, slowly the upload will work. I guess for users with a small collection it works fine but for the serious user's it needs to be made much more reliable and configurable.
4
Replies
AdChoices