Luminar 4 4.3 - low editing performance for files with multiple changes applied / long editing history
AnsweredYesterday I've updated Luminar from 4.2 to 4.3. At glance editing performance is significantly better (cool!). However, not for files with a significant amount of changes applied.
I opened a few DNG/RAW files (small ones, about 25-30 MB each), and for new ones, with no editing history, sliders move smoothly and changes are introduced almost instantly.
For images with e.g. with 30-40 entries in operations history (note: some of them are like "Denoise enabled" and just after that "Denoise disabled" so finally change is not applied), Luminar 4.3 acts slowly.
I see "Image processing" for up to several seconds even when I am adjusting e.g. exposure. It looks like it walks through all the history entries and applies them one by one each time. In the task manager, I see almost full CPU workload (about 87-90%) so almost all processing performance is used. But still, it shouldn't work this way on high-end PCs (see specs below).
Switching between and opening RAW files is slightly faster but I don't feel it's the update I was waiting for - still far behind competitors' fluency.
I haven't checked that yet, but I hope memory leaks are fixed as mentioned in the changelog. Recently, when I tried to process a bunch of images (not batch, just manually one by one), I saw that I have used 45,7 GB of RAM (!). I had to close Luminar (4.2) and open again to release 25 GB of RAM.
What I like - look preview on mouse hover without a need to apply it and undo changes. That's cool!
I performed tests on the following PCs:
1)
- Ryzen 5 3600 - 6 cores/12 threads, holds 3,95 GHz on all cores under full load;
- 64 GB DDR4-3200 RAM working in sync mode with Infinity Fabric bus;
- 2 x 512 GB SSD NVMe with 3,3 GB/s reading and 2,3 GB/s writing performance (system and photos/library placed on them);
- GeForce GTX 1660 with 6 GB VRAM;
- Windows 10 (1909, build 18363.959) with the latest updates and drivers (including chipset, GPU, and UEFI).
2)
- Ryzen 9 3900X - 12 cores/24 threads, holds 4,1 GHz on all cores under full load;
- 64 GB DDR4-3600 RAM working in sync mode with Infinity Fabric bus;
- 1 TB Samsung 970 EVO Plus SSD NVMe with 3,5 GB/s reading and 3,3 GB/s writing performance (system and photos/library placed on this drive);
- GeForce RTX 2070 Super with 8 GB VRAM;
- Windows 10 (1909, build 18363.959) with the latest updates and drivers (including chipset, GPU, and UEFI)
On both configurations, I experienced the same issues. As the second one is much faster than the one you've been using for testing purposes (I mean https://prnt.sc/thdb14 I found in pinned thread related to release), I am letting you know, that there's something you should investigate if it is not a known issue already placed on your roadmap.
Anyway, I now feel I can go back to my photos taken nearly a year ago as Luminar 4 started working well enough to do some basic edits. I keep fingers crossed for the future updates as more complex works that require a lot of changes still make L4 notably slow even on fast PCs.
-
Official comment
Hi Jacek,
Thanks so much for sharing your feedback! Improving Luminar 4 performance is our top priority now, so it will work faster with each update. I'll pass your feedback to the team in charge.
Thanks so much for bearing with us while we're making our software better.
Comment actions
Please sign in to leave a comment.
Comments
1 comment