P: Running with 200% scale for the UI degrades performance

I've contacted the Action author and asked them for a copy of the actions for testing purposes.

Hi Adam. Unfortunately, the actions I am using are not of my own invention. They are Florabella Colorplay actions that I purchased, and the terms of purchase specifically prohibit sharing. I will grant that these actions are instigating a lot of changes at once on very high resolution images, on a very high resolution screen. It would make sense that they would be slower overall when compared to their performance on a lower resolution display, however I still fail to see how activating the 200% UI feature can cause such a dramatic slow down. This feature is only enlarging the UI; the canvas size and all elements of the image being changed should hypothetically remain the same, correct?

Michael,

Is there an action you can share that's running slower in 200% vs 100%? I just ran some quick automated performance tests and didn't see much of a difference between the two settings. @ 200% we are pushing way more data around (compared to 100%) but it still shouldn't have a significant impact on your workflow.

Thanks,
Adam

If there is anything I can do to assist, I'd be more than happy to. Thanks, Jeffrey.

Thanks. I've asked our performance testers to take a look and see if we can reproduce.

I have tinkered around with this feature a bit more, as I would truly love to move out of my CS5 software and utilize my 4K display to it's fullest. I have spent the last 2 days playing with every setting imaginable on my system and in my PS CC 2014 software. I have the performance of CC almost identical to my CS5 in every way while using 4K and disabling the 200% UI feature. Actions run comparably, and all features check out. Enabling the 200% UI feature, for some reason, doubles my wait times on every action I run. I definitely appreciate the 200% feature, and respect that it is a Experimental Feature (I can't wait for the Bridge team to at least make it this far), however doubling my workflow for the sake of utilizing my screen to it's full potential is illogical. Back to CS5 and standard high definition editing I will go.

But rest assured, when the scaling issue is sorted out with PS CC and Bridge CC, I will be the first in line to subscribe!

The only thing that makes it slower is initiating the 200% UI feature. If I disengage it, it is comparable to CS5 speeds, though still notably slower- if I activate this feature, it slows down unbearably. The resolution is the same while running both programs, the only variable is this feature. I am running the same preferences as I was in CS5. Also of note, the speed on CS5 doesn't change regardless of the resolution. My system is in good shape, I don't know what would be wrong there. Just sharing my experience, if there are additional details I can provide to be of assistance I gladly will.

That needs a new topic, as it has nothing to do with this topic.

As a result of problems, I had a CS rep give me a couple months free subscrip to CC or whatever, in a tel conversation, but my account is still billed in the month after. Adobe has problems deeper than consideration for its hi-rez customers.

The dinosaurs never saw it coming.

OK, for everyone else CC runs faster or the same as CS5. So you need to check your system to see what might be slowing down CC.

And yes, drawing on a high res display is a bit slower than drawing on a low res display - which can be hidden by a good GPU, but not all GPU drivers are yet optimized for high res displays.