Skip to main content
Inspiring
May 11, 2014

P: Library Module slow performance: FIX found!

  • May 11, 2014
  • 45 replies
  • 1144 views

I've found a solution to a problem many others seem to have reported - but it does involve a work-around, suggesting the Adobe Photoshop Lightroom team need to fix a bug.

When a large number of Develop Presets are loaded into Lightroom (in my case, over 500), the Library Module, and strangely, to a lesser degree, the Develop Module run very slow.

Having performed some troubleshooting, I discovered the reason for the slowness was a CPU spike. On my iMac 3.4GHz with 32Gb RAM, NVIDIA GeForce GTX 680MX with 2GB, and 1TB Fusion Drive, the CPU would go over 100%, while the disk and memory allocations were low. I run Mavericks 10.9.2, so it's not a matter of an out of date OS. This occurred whether I had 10 images or 10,000 images in the catalog (I tested various scenarios).

I read on a forum that the number of Develop Presets could affect performance, so deleted the majority of them (backing them up first) to see if it would make a difference. I reduced the number of presets to less than about 100, and the performance increased INCREDIBLY and INSTANTLY.

So, it would seem to me there is a bug in the way the Develop Presets are being indexed in Lightroom. Hopefully, this is something the team can find and fix very easily, as it should be easy enough to identify the root cause and reproduce the problem.

Please, Adobe - release a fix for this in the next point release. It is disappointing not to be able to keep all my Develop Presets in a single session. My work-around is to exit Lightroom, copy in the Presets I need for a job, then start the program again. Obviously not ideal.

Many thanks,

Matthew

This topic has been closed for replies.

45 replies

Participating Frequently
June 5, 2014
Hi Mike, thanks for pointing me at that thread.

-Ben
Inspiring
June 5, 2014
Notably, Mike is on Win, I am on Mac.
Participating Frequently
June 5, 2014
Hi Ben
I assumed that there was some type of relationship.
The topic already exists:
http://feedback.photoshop.com/photosh...
Mike
Participating Frequently
June 5, 2014
@mike117235:

Unfortunately, performance is not a single issue, it is a vast array of issues, which must each be carefully defined and addressed separately. If you're experiencing a degradation in import performance in 5.4 vs. 5.3 (which is not at all what this thread is about), I would suggest you start a new thread on that topic, with as much detail as possible.

@ Matt:

On a much lower end machine than yours, I notice no degradation whatsoever when using 1,000 of your presets, and very little when using 2,000. If that is different than your experience, then there may be a separate issue here. Let me know how many presets you feel you can have before you start to notice a performance problem. There may be some diagnostics we could run on your machine that might shed some light on the matter.

Thanks,
Ben
Inspiring
June 5, 2014
Thanks @Ben107584,

For clarity, I do not need or use all of those presets together at any one time. I sent you my entire library to make sure none of them were corrupt.

I take your point regarding the number of presets loaded at any given time, and how 7K represents something of an edge case, however I have tried this with far fewer (less than 1K) installed and still had issues. It was only when I removed the vast majority of presets that the performance improved.

In that regard, Mike has highlighted there may be two independent issues here, which makes me suspect it's not as straightforward as first thought.

That said, the team should be able to identify the root cause of such issues using code profiling.

Thanks for looking into the issue - I do hope the team will continue looking at ways to improve product performance. Photographers are a hungry bunch!

Cheers
M
Participating Frequently
June 5, 2014
Hi Ben

I have the same speed issue, but presets are NOT my problem. I have around 1500, but when I remove them all (as well as camera profiles from packages such as VSCO), my import is still abysmally slow compared to 5.3.

Therefore, I'd ask you to please NOT think that this issue is solely related to the number of presets.

To clarify, I had the same number of presets etc. with 5.3, and there is no issue.

PS I have a high-end windows machine, quad processor, 16GB RAM, and I work off an SSD.

Thanks

Mike
Participating Frequently
June 5, 2014
Hi Matthew,

I have done some testing and have confirmed that you do not (so far as I can tell) have a corrupted preset. I believe you are correct, it is simply the large number of presets that is causing Lightroom to perform poorly.

However, your statement that you have "over 500" presets is, while true, a bit of an understatement. You have 7476 presets which, I'll be honest, is quite a bit more than I had previously tested (I'd only tested up to about 1,000 presets).

How many presets you can have before performance drops off obviously depends on a lot of things, in particular how powerful your machine is. On my relatively low end test machine Lightroom was still able to perform reasonably well with 2,000 presets.

So, I will bring it to the team's attention that performance degrades with large numbers of Develop presets. But I want to be honest up front, I imagine that the team will probably consider having 7476 presets to be something of an edge case, and fixing this may not get top priority. So in the meantime, if you can limit yourself to your favorite 2,000, you should be in good shape. Heck, if you can go crazy and cut it down to 1,000, things should be really snappy. :-)

Thanks,
Ben
Inspiring
May 28, 2014
@Ben107584,

Haven't heard anything from you since I sent you my presets. Any further word?

Clearly, I'm not the only guy shouting about this - and it seems others have verified the solution works for them also.

Would be good to get an update from Adobe on this issue.

Thanks
Inspiring
May 28, 2014
I'm currently just living with removing the presets all the time. Let me know how it goes with C1, I'm not currently a big fan.
Participating Frequently
May 28, 2014
Hi Erik
I'm in a similar position and also looking at C1. Editing is nightmarishly slow because of this issue.
Mike