I was exporting 50 photos on my newly built Core I7-3770 machine, which is a CPU has 4 cores 8 threads. From the task manager, I noticed that only 50~60 percent of CPU was used.
If exporting 1 photo only takes half of the CPU power, why not Lightroom process 2 or more photos at one time for those systems have extra power?
I'm running a quad core i5 with 20GB ram and a 500MB/s SSD(neither is maxe'd or even taxed), the max processor use I ever see is 300% fluctuating greatly. Seti@home runs 4 instances of itself, PEGS the processors at 400% (100 each) for days on end and still manages to gracefully allow other programs (even photoshop) to work normally like a well written background process should. Perhaps Adobe could consider making a hefty donation to Seti@home for them to optimize their photo applications for multi core processing?
Dear Adobe, please respond to this post. I think all we want is an honest answer as to why your program does not work in this fashion. If you are working on it, wonderful. If you don't have enough resources, let us sign up to support this initiative. If there are other considerations we have not brought up, please discuss.
I'd like Lightroom would definitely make something better with my CPU, multithreading and multitasking itself. Speed up the exporting process or let people make a good use of OS multitasking capabilities!
E.g.: I'd like to work on a different catalog (a different wedding for example) while exporting my 1.000/2.000 images set(s) of the first catalog.
exactly! You can force lightroom to do this by breaking up your export into several groups and exporting them simultaneously... For the record adobe camera raw when hosted in 64 bit photoshop exports photos in the way we're requesting.
This would be ideal! leave it up to the user. There are times that you want to be able to use your computer for other tasks, and there are times when you would prefer to max out your system resources to finish your export asap.
When exporting a webgallery the workaround to do it in several parallel jobs often doesn't work (as it does with the normal picture export).
For me this means that the hint can just be a workaround and Adobe should focus on optimising the use of ressources with multicore computers.
I've similar issue during importing more then 2,000 files:
Windows 7 SP1; 64 Bit
Intel i7 with 4 cores, enabled hyperthreading and 3.6 GHz
-> 8 virtual CPUs
24 GB RAM
Only up to 25 % of my whole CPU resources used by Lightroom, so it took up 20 minutes.
If it would use all cores, it could do it 4 times faster: also only in 5 minutes!
Some for updating the previews after changing pictures. One preview after the other was updated. No parallel processing. Only simple and slow sequencially processing.
I'm really disappointed, as multi core CPU are not rare anylonger since years!
I suspect it's that it's using a single export process and multithreading the filters it's applying but some are only single threaded. So it's 100% when it's a really efficient algorithm, and low when it's single threaded (zip compression for example)
One caveat: does not support export filters (post-process actions), so export preset must not include references to Lr/Mogrify or Exportant..
Otherwise, any export preset can be used, and it will work the same as if export preset chosen in export dialog box, except for the multiple tasks (and sequence number override).
really great, Rob!!
But as this script can only speed up "mormal" export but for example not the export of a big web gallery with many pictures, I'm still hoping on Adobe to optimize Lightroom performance and multi-core usage in the Lightroom core code.
Thanks for posting this here Rob. I'm trying the export script and LR is consistently using 95%+ of my processor and nearly 5GB of RAM. LR seems to have inefficient coding and on top of that it won't use available system resources. This at least solves the last problem. So, thank you!!
** as a reminder to anyone else using this, LR won't release RAM until it's been restarted. So, to keep everything running smoothly restart LR after a big export. WHY????
You bet Dan, and yeah: if you are memory-challenged in the first place (whether due to amount installed or non-optimal memory-management/bugs..), this script may make things worse.. - in addition to using more CPU, it will also use more memory doing exports in parallel than sequentially. Lr *should* release used memory, but as most of us know - it doesn't always..
FWIW: This script only supports (non-publishing) exports without post-process actions, it does not support publish services, nor web galleries.
hopefully Adobe will be inspired by the real world results of your script and apply this to standard preview generation (smart previews build so much faster) and web pages and books and so on.
hi, could someone please tell me how to install the export in parallel scripts in lightroom? or even how to get it. i used to have it before but after i cleaned my hard drive and installed windows again i lost it and cant find it anywhere.
57
Replies
AdChoices