OK, I tried changing the affinity settings as per SavaPhoto's suggestions and...well what a difference that made.
HIGH and 0,2,4.
It's highly usable! I mean it's not lightspeed but it's on par with the previous version, like a breath of fresh air.
Now THAT is an interesting solution....I'm not imagining this it's gone from dragging through mud slow to skipping and bopping like an 80's mental patient.
While in LR4, CTRL-ALT-DEL
Start Task Manager
Find Lightroom under the Processes tab
Then change priority to high
Then select Set Affinity and deselect everything except 0,2,4. Experiment though, it'll be interesting to see other people's feedback.
Jos do you know how to make a .bat file?
Open a txt editor like notepad type this line
start "lightroom" /high /affinity 5 "C:\Program Files\Adobe\Adobe Photoshop Lightroom 4\lightroom.exe"
Be sure to change the path to your lightroom path if its different - make sure to leave the path in quotes. Save the file as lightroom.txt and rename to Lightroom.bat . then when you click this Bat it will run lightroom on core 0 & 2 . Let me know if you have any problems.
Chaning priority and processor affinity doesn't make an appreciable difference on my i7-930, W7 64-bit, 12G RAM system. But I didn't have a significant speed issue.
Maybe we're getting to the heart of a processor-dependent issue? (I was going to say the core of the issue...)
When a support person says something is corrupted they usually mean:
a) We changed stuff and the problem went away but I can't be bothered to figure out why so let's call it corruption
b) I know what the problem was but I'm not allowed to talk about it so let's call it corruption
The preferences file is just plain text so real corruption is easy to spot and I would expect LR to spit out an error if it had any trouble parsing it. I suspect that something written to the preferences by a previous LR version was tickling an issue in 4.1 on your system but that is not corruption.
For the record, the suggested affinity change did nothing for the LR 4.1 slowness problem on my Dell 32bit Win 7 Pro PC. Corruption, problem or whatever you want to call it, it's slow and should not be this way - it needs to be fixed on machines that continue to have this condition.
dbeifeld - it still doesnt fix my issue but does make it more useable. Until tonight when I did some math and this is what I posted to another forum -------some simple math tells me that if I loose only 5 sec an image on average - which is likely low since at a minimum I probably loose at least 1 second for every adjustment and photo change, than I will loose about 1.4 hours for every 1000 photos I process. I am currently working on 3 sessions which total about 7000 photos. That is more than a whole days work GONE. I will loose at least one day a month and at least two weeks a year for a one second lag. So one second might not be slow to some but to a busy pro trying to make a living in the flooded field of photography it really is unacceptable. Today I have spent most of the day trying alternatives to lightroom.-------
Just for reference I'm running the 64bit version of LR4.1.
Also comparable to before where spot removal was totally useless for me, the temporary fix changes I have made above have completely changed the program, click spot removal, click a spot and boom, done, next click, done, click, done as it should be.
Before has me suffering huge delays.
I'm not hating on Adobe, I would have Adobe's babies but there's a pattern forming here, from reading this forum and others, that seemingly Windows 7 64bit running i5/i7 cores and LR4.1-64 have enormous slowdowns, which can only lead to coding.
LR3.x no problem, LR4.x, BUP BOW.
Just to make it messier for you, I have the same issue, but I do NOT have a Intel i5/i7 on this machine. Win7 64 bit 8Gig RAM SSD w/ images on sep drive AMD Phenom 9650 Quad 2.3 GHz. Clean load, never had lightroom before. My laptop with a mobile i5 performs better with everyone on 1 drive. I suspect the issue is with 4+ cores perhaps? I tried the affinity trick, and didn't help sadly. Just saying. If nothing else this thread as been an interesting read
Europe, Middle East and Africa