Lightroom: LR 3.5 & LR 3.6RC hog up all cpu power at export and develop mode.

  • 1
  • Problem
  • Updated 6 years ago
  • (Edited)
Using Lightroom 3.5 & LR 3.6 RC with Snow Leopard (system up to date), Macbook Pro early 2011, 8 Gigs RAM.

Both Lightroom version still hog up all CPU Power on export and when in develop mode - here even if i just browse my collection in develop mode.

In both cases the CPU goes high and heating over 90, 105 degree celsius and the fans are going over 6200 rpm crazy. The MBP sounds like a vaccum cleaner!!
And it takes forever until LR releases the CPU for other tasks and the spinning color wheel showing up forever.

I did already did an SMC reset and all the other troubleshooting that the Mac support suggested me.

No problems with other Applications from other software companies so i can assume the my system is fine.

This is just ridiculous and very unsatisfying user experience.

Below that terrible experience: Exporting only a few Images from LR with standard settings (no resizing, no sharpness, nothing) is STILL SLOW AND STICKY like grease.

Wasted money if you ask me!
Photo of Final Cut User Group

Final Cut User Group

  • 7 Posts
  • 0 Reply Likes
  • frustrated

Posted 6 years ago

  • 1
Photo of jdv

jdv, Champion

  • 728 Posts
  • 55 Reply Likes
Well, Lightroom will ask for all the resources it can get. It is supposed to be up to the OS to throttle that, if necessary. That is, it really doesn't matter if the CPU is being spiked if nothing else is asking for it, assuming that Lightroom is not cycling hard on a busy wait.

You also might have a failing hard drive or something, if this is related to the swap file(s).

The take-away is that Lightroom is probably the single most memory, CPU intensive app you own and run on a regular basis. It will use all the resources that it can ask for.

Here are things to try:

- Disable all plugins and restart Lightroom. Try to reproduce the problem.
- Create a test login and try there. This rules out login specific stuff. This is tricky because you have to either create a new catalogue and import a subset of your photos (unless you can duplicate with a simple test export) or copy your catalogue to the new account.
- Collect a number of "samples" of the Lightroom process when you think it is spinning or lugging. You can find this via the Activity Monitor app.
Photo of Jeffrey Tranberry

Jeffrey Tranberry, Sr. Product Manager, Digital Imaging

  • 13968 Posts
  • 1664 Reply Likes
Photo of Final Cut User Group

Final Cut User Group

  • 7 Posts
  • 0 Reply Likes
Yes i've been going trough several google sessions to find out that i'm not alone.

Listen, LR system requierements are:

Mac OS

Intel processor
Mac OS X v10.5 or v10.6
2GB of RAM
1GB of available hard-disk space
1,024x768 display
(CD-ROM drive)

So, no one ever was talking about horrenduous amounts of RAM and CPU power and neither of sick expensive SSDs

I am tired of reading adobe "Optimizing ... bla, bla"
This is just crazy, After effects for example has a shitload of resource to read about optimizing performance here

http://help.adobe.com/en_US/aftereffe...

here

http://forums.adobe.com/thread/543440

here

http://blogs.adobe.com/toddkopriva/20...

and probably some more somewhere on the world wide web ..

Loo, i'm not here to provoke or ranting around, but you have to be honest, if i take a look at my brand new Macbook Pro and it's performance, then looking back to LR System Requirements and compare the actual Performance LR acually gives, i have to admit that you product is sold as a lie.

I see this problem with several different Adobe Applications. You put more effort into more popular software and leave all the other lagging behind.
Illustrator and After Effects is one of the best (negative) examples.
Seriously, if i'd work at Adobe, those two teams would be the first that i'd tear of their heads and then the LR Team. I do not beleive that you people are using your own software every day in a (paid) working environment. Otherwiese you would have found out all the flaws pretty fast.

Sorry coming here with that bad vibe but hat's my conclusion about Adobe Products and I'm pissed because I have wasted several days now to cope with the problem stated above and it's definitely a software issue.

Bye.
Photo of Jeffrey Tranberry

Jeffrey Tranberry, Sr. Product Manager, Digital Imaging

  • 13932 Posts
  • 1653 Reply Likes
You may want to take a look at the community guidelines here: http://getsatisfaction.com/help/commu...
Photo of Final Cut User Group

Final Cut User Group

  • 7 Posts
  • 0 Reply Likes
I know what you want to say to me.
But those guidelines actually won't make a change of the actual problem!

That's all folks. There isn't anything more to say than everything already stated above.

If it helps you (the software creator) solving problems, fine.
If not, toss it.

"You have to break some eggs to make an omelet"
Photo of Rob Cole

Rob Cole

  • 4831 Posts
  • 371 Reply Likes
|> In both cases the CPU goes high and heating over 90, 105 degree celsius and the fans are going over 6200 rpm crazy. The MBP sounds like a vaccum cleaner!! And it takes forever until LR releases the CPU for other tasks and the spinning color wheel showing up forever.

This is not normal. I mean, yes: Lightroom is a resource intensive program, but no: 100% CPU utilization for long periods, and over-heating CPUs... are indicative of an unusual problem. - The wheel should never spin for more than a few seconds or that's another indicator of an unusual anomaly.

If you ever cool down and want to have another go at it - we'll be here to help...

There is something about your system/install/config... that's not copacetic with Lightroom.

btw - I had a similar problem when I tried Aperture (on an otherwise seemingly healthy and relatively virginal standard-issue Mac) - raw adjustments took minutes to process - never resolved since I didn't deem it worth the effort... - I know most people don't have that problem, still...