P: Quick Develop VERY slow on my system (6 sec vs 1 sec in LR 5.7)

YES!!!! This is a huge improvement!!! THANK YOU! It almost feels like I have a new computer. This will save me so many hours of work! 😄

Today I ran Lr CC 2015 6.1.1 on a large project on my Win 8.1, i7 3.6 GHz, SSD, 32Gb, nvidia GeForce GTX 770 PC and the performance issues are still there. Checking "Use Graphics Processor" still results in the same clunky performance.

Working with a simple Radial Filter CPU usage was a solid 100% with "Use Graphics Processor" checked and around 35% with it unchecked. Export delivers a solid 100% CPU usage with or without "Use Graphics Processor" checked.
Serious work will still need to be done in the flawless performance king, Lr 5.7 (on the same tire-shredding machine).

It's been suggested that uninstalling/reinstalling Lr could be worth a try.

I am pleased to report my slowness issue seems to be gone with the new release (2015.1.1). It is blazing fast. Thanks for the effort to fix it and keep improving both version CC and 6.

Simon, would that mean we *could* expect even better performance in that future dot release?

At last LRCC 2015 is as fast at rendering previews (particularly 1:1s) as its predecessor LR5. And it does not slow down to a crawl after several hours, which it did before this update.

I suppose 1 step back and 1 step forwards is progress!!

Thank you for the response Simon. I do developer support, device drivers.. So when things don't work. I like to hear it from a dev. someone that knows the details. Thank you!

That would also if I understand how you build the product, explain in many ways the performance wasn't really changed with GPU enabled or disabled. But executing AVX/AVX2 cpu instruction streams are still going to be used if the code thinks its safe to use them on the CPU.

I can live with this answer to rebuild the exe's and DLL's w/o the code generation.

Now I need to know (email privately if required) you tell me how to get real diagnostic output as to why the GPU test is now failing.

Ron

Good to hear.

The earlier performance degradation of AVX/AVX2 on Windows was due to a code generation issue in the earlier version of Visual Studio compiler.

Upgrading to the latest version of Visual Studio is out of the question for the Lr 6.1.1. At least the performance should be back to where it was for Lr 5.7. Rest assured the correct AVX/AVX2 performance optimization will be back in a future dot release.

Yeah this 6.1.1 update really seems (so far) to address the major issues outlined in this topic and thread. Nice job LR dev team. Good update!

The update solved the problem, thank you so much!