54
Replies
Question: Is it "only" a Mac problem? If some Windows users are reading this: do you also aware super low performance on PC?
@Adobe: must be a problem with the CameraRaw engine for Mac. I makes no difference working with Lr or CR on an image, both will burn out CPU and GPU, you may boil water with the heat produced, Software is the opposite of performant.
I am developing software since 1986 and at the i286 and i386 times, there have been code analysing tools called "Profiler", you find useless performance wasting subroutines instantly. It was essential for performant software at those time. - And it is still, there is no such thing like infinite hardware resources. But I am afraid, today's drag and drop software developers have no clue of how to do Profiling checks on a piece of software and make them performant.
With my 33 years of developing software experience I may testify, in 99.9% of performance problems it is a tiny subroutine/function (mostly only 3 to 5 lines), accidentally called 100 or 1000 times - even if a single call would have been sufficient.
The remaining 0.1% is waiting in a totally false way to an input event like e.g. "OnMouse{Whatever} do …".
The performance and battery drainer of Flash, since Adobe acquired Flash form Macromedia exactly having such an error included. Stupid to have all Macromedia developers fired. The problem still exists in an 16 bit object code used since then, because the source code got lost on acquisition. You still may easily find Macromedia strings in that object code with a debugger.
In case of Lr/CR performance problems it is guaranteed the 99.9% case. Experience is the heck of a good thing. 
Damned, Adobe, get this performance problem fixed instantly!!!!
It's exactly the same with windows (8.1 pro in my case).
Had to wait 4 minutes just to get it started. System and LR catalog are on a fast SSD, top-of-the-line CPU, 32 gigs if RAM.
I'll try to downgrade... when this thing will eventually shut down 
Can you check if Face Detection is enabled?
Can you check Lr is Syncing with Cloud?. If it's running then use 'pause' option in ID panel at top left of Lr window (see Issues after updating to Lightroom Classic CC 7.2 for more details)
Also, run 'Optimise Catalog' from File menu
Has never been enabled on my systems:
https://forums.adobe.com/people/Ian+Lyons wrote
Can you check if Face Detection is enabled?
Can you check Lr is Syncing with Cloud?. If it's running then use 'pause' option in ID panel at top left of Lr window (see Issues after updating to Lightroom Classic CC 7.2 for more details)
Also, run 'Optimise Catalog' from File menu
No, Face Detection is disable and Sync whit cloud is disable.
I repeat, I use Mac (iMac 5K 2017, CPU i7 4.2 ghz 32 GB Ram and Radeon Pro 580 8GB GPU) and after a test with Activity Monitor, the CPU and GPU levels are very high, the Mac overheats, the fans start and everything Slows.
It is an excessive consumption to be used with Lr
Furthermore, by creating a new catalog or using Jpg instead of Raw, consumption is always very high.
In my opinion there must be some mistake in the design of Lr itself
https://forums.adobe.com/people/Ian+Lyons ha scritto
Can you check if Face Detection is enabled?
Can you check Lr is Syncing with Cloud?. If it's running then use 'pause' option in ID panel at top left of Lr window (see Issues after updating to Lightroom Classic CC 7.2 for more details)
Also, run 'Optimise Catalog' from File menu
Ian, this is done quite often automatically and does not solve the problem:
It is like I wrote above, Adobe developers must use a "Profiler" on their software, and if they don't know how to use it, they can hire me as consulting engineer, I will show them.
I already like to see the jaw dropping faces of them, if I could show to them, how easy it is to detect bottle necks and to resolve such problems efficiently.
It is not about to pass the buck to someone, bottle necks just happens accidentally on almost each piece of software having more lines of code than
main() {
printf("Hello World!\n");
}It is my daily business since 1986.
More than 100% CPU is caused by multi core architecture. Each one count's 100%. Depending on i5, i7 etc, this is possibly presented different by Activity Monitor, e.g. on my iMac 5K with 4 GHz Intel Core i7 and AMD Radeon R9 M395X 4096 MB it looks like so:
Not so nice is the CPU and performance and power consumption just switching ONE solely 24 Mpixel image from Grip to Developer mode, each vertical bar representing 5 second interval. More performant and for that power and environmental sustainable is something else.
Adobe, please open your eyes, there is also the GPU history displayed in the lower field and GPU usage is activated in Lr preferences. But it looks like GPU is not used at all...
AdChoices