More information that may help. I am running a second monitor, 27". I had the second window checked on (2) to my MBP. It was in Loupe view. When I clicked off the second window and just used the 27" monitor the sliders worked smoothly and changes are almost instant.

If the second window (mbp) is in grid view it is a little slower, but really slow in loupe. I'm happy again. It was so frustrating I was not going to play 4Beta anymore, now, I'm back at play.

Hope this helps.

JIm

Slider responsiveness is very bad on my PC as well. And I also think that scrolling through pictures in Grid mode is extremly sluggish and always was in previous versions. Scrolling through hundreds of pics is just a pain, like in LR3, 2 and 1! I have been playing with Capture One 2.9 yesterday on a single core Pentium 4. Everything I did, no matter wether it was scrolling or adjusting sliders, was realtime! Now software is more complex, but Capture One with OpenCL still is very snappy and fast! That`s what I expected from Adobe as well, since we see the complaints about slider responsivness and scrolling in LR since ever.

Jim Stamates wrote:

 

...Then I might as well go get a beer before the image changes.

 

Jim

I think I get it now - this is actually part of the new feature set.

I have it another way around on windows 7 64bit. The slowest is the startup and the first module switch. Often an empty video player shows up hanging above other controls, sometimes just empty black rectangles. It hangs for about 20 secs, but the process does nothing, no cpu or hdd activity. at the moment it is respondible again, the memory usage increases significantly, and the app functions as if nothing happened. The strange thing is, that even lr3 behaves now like that, and it never did, until i installed the beta.

vmtr the problem is not that the performance is not fixed - its even getting worse. i love lr3 but it is getting worse and worse. i KNOW this is a beta and i know this will be improved, but i really doubt that they can bring a product that runs fluid and fast. i am a realist. in py opinion you have the choice. unbelievable features and good options but slow or spped and not so gut features. i tried capture one and it is fast as hell on my machines, but does not have all the functionalitys like LR and is not so comfortable. but to be honest the skintones in capture one are really good compared to LR. color checker passport can fix this problem anyway.

Another thing i want to suggest - people when you say your performance is good, tell us also what raw datas from which cam you work with. i have not heard from ANY person who works on huge 5dmkII, 1dmkIV, nikon d3s and so one  raw files, that are nor completely dissapointed from the performance of lr4 beta and most of them are dissapointed of the speed of lr 3,6 too, even on quite fast machines. Working on a native eos 550d raw files runs completely realtime on my machines - in lr 3,6 and in lr4 beta in pv2012

king regards chris!

Similar sluggishness to OP here. Core i5, x64 Win7, 8GB, SSD. Only imported 64 example DNG files, previously processed by LR3.

I haven't tried moving to the 2010 process apart from on isolated photos, but anyway my user experience is overall extremely slow, not just in the Develop module sliders, with visible window/dialog repainting and sometimes the Windows busy cursor appearing for simple operations. Even just minimizing the app and maximizing it again results in a noticeably slow repaint compared to other Windows apps. 

It's usable, but not very pleasant, and much worse than 3.6. Like a beta that's still running debug code or something (but it's probably something else; this is just what it feels like to me).

For me it does not matter what the file size or type is or how much ram you have because photoshop CS5 or even CS6 beta doesn't have a lag problem using the same type of brush adjustment or spot fix that does lag or lock up in Lightroom. If I want to repair spots or touch up a face I am forced to change to photoshop to get the job done.

vmtr wrote:

 

For me it does not matter what the file size or type is or how much ram you have because photoshop CS5 or even CS6 beta doesn't have a lag problem using the same type of brush adjustment or spot fix that does lag or lock up in Lightroom. If I want to repair spots or touch up a face I am forced to change to photoshop to get the job done.

While it definitely helps to keep sharpening and noise reduction zeroed until the bitter end stacking up the adjustment brushes still becomes a painful experience.  What I've also noticed is that you need to keep your foot on the gas once you start your brush strokes.  The processing seems to stabilize and you can paint fairly clean if you maintain a continuous stroke.  But as you soon as you lift the pen (or release the mouse button) and interrupt the stroke then the engine does it's thing and will take time to catch up when you start to brush again.  Like pedalling uphill with momentum behind you vs. stopping and starting again.  Awful.  Forget about feathering in an adjustment with low flow.

Granted, Lightroom has a lot more gerbils spinning on wheels than does just ACR but I sure like the immediacy of Camera Raw when it's running on its own (ie. out of Bridge or Photoshop).  That's how Lightroom should flow in the Develop module.  Clean and real-time.

Adobe reads threads here, and some known bugs in this area have been mentioned here.

There's not much to talk about on this issue.  There are performance problems with the beta.  We know that, and they know that.  They have to fix the performance bugs (such as the one that causes massive slowdowns on upgraded images) and optimize as best they can.  Period.

Look, I could give a rat's tail end about maps and photo books in this application. It's all fluff that makes me fearful of what kind of stress it's putting on the whole of the engine. But Adobe isn't making the app for just me and the Lightroom team isn't new to this game. This is their 4th major public beta go around and they have had to deal with this every time (especially with the performance issue before it's baked). the performance issue is something that the team knows about, know's that they can't release a final with these problems without all hell coming down on them from every pro (and other) that has to depend on the program managing their lively hood. We all want it to be perfect out of the box... the thing is it hasn't been put in the box yet. The more time they spend managing our issues with a program that we shouldn't be using except for a geeky fun time play toy, the less time they have to actually get the work done. It's perfectly reasonable that they are going to talk about the features that they are still making the recipe for (whether I want those features or not).

So when is the second beta coming out?

Simon,

the sluggishness is a problem with LR since version 1 and IMO has very little to do with the beta stadium of LR4. If the sluggishness would be really be adressed, than LR4 would have to be a lot faster than all previous LR versions,.....what I seriously doubt.

Lr4 seems pretty good (for a beta) and most of the performance is comparable to Lr3 (which I find totally acceptable on my system: Core i7-2600 3.4ghz, 16Gb RAM, SSD system disk, 2x1Tb HDD in mirrored RAID array, Radeon HD6850 1Gb). The only sluggish thing is switching modules, e.g. "slideshow" to "print" is very slow.

So far I could'nt  find any difference to LR3, means same performance. Tried the stamp, brush etc. where others reported bad performance.

Working on an Core I7 Q 720 @ 1,6GHZ, Win 7 64bit, 6 GB RAM.

Oli