Photoshop CC 2020(21.2) : App literally became critically slow with frequent stuttering

  • 36
  • Problem
  • Updated 2 days ago
My specs for the test :
CPU : Core i7 3610QM
GPU : Nvidia GT 640M
Drawing tablet : Huion H610 Pro
PC Model : Acer Aspire V3-771

Greetings Adobe. 

You really have plenty of optimizations problems with all the features and changes you apply to Photoshop, and this since you left Creative Suite 6. I don't know what's wrong with you. I say you should optimize Photoshop so that, at least painting performance stays smooth even on an Intel HD 4000 GPU with a 2nd gen Core-i5 CPU. Yes, those are less than 10 years old specs but strategically speaking, your developers should know why, it's the best way to manage how well you optimized your app or not. Seriously.
So if you don't make tests on a 10 year old or less than 10 year old machine, performance problems will remain. And it's just unprofessional to hide them just because y'all have GTX 1050 GPUs with last gen Intel Core CPUs. It's unprofessional to have your app slow down in performance when its newest features are not used at all. I'm talking about rendering fps and painting performance regarding speed of execution.

Anyway, I tested v21.1.2, v21.1.3 and just now v21.2... And I don't congratulate you at all.
Now Photoshop became slower and gives constant stuttering for its rendering performance. It's to the point that I can't even imagine using it anymore. 
Just how do you even optimize your code and algorithms ? 

I was curious today for something else as well. I tested Photoshop CS6 after installing it. And guess what ?
Photoshop CS6 was running butter smooth. And some of the problems caused by your newest features to the point that you broke your wintab implementation in latest versions of Photoshop, were absent ! I was using wintab and painting strokes was 4 to 5 times faster and smooth than in Photoshop CC 2020. Plus there were no stutter at all, and this was on a 5x7.5 inches canvas at 600 ppi resolution.
The reason I'm saying you broke your wintab implementation is because there's an exponential performance fault that is proportional to the time I spend painting any single stroke I'd hold for a long time(more than 20 seconds) without releasing my pen pressure on the canvas.

If performance was this good and smooth in Photoshop CS6, I see no reason for it to slow down or get broken in Photoshop CC 2020 or even Photoshop PhCC 2021. Adobe, It's obvious that your developers broke things in Photoshop to degrade its performance. New features is OK, but they should never impact negatively the previously known good performance of a software. Unfortunately, this is what I'm seeing right now.

Anyway, this was a test report. You will consider this issue if you care about the quality of Photoshop.
Photo of Ed

Ed

  • 30 Posts
  • 3 Reply Likes
  • frustrated

Posted 2 months ago

  • 36
Photo of David Bleja

David Bleja

  • 110 Posts
  • 58 Reply Likes
Drumming on about CS6 won't get you anywhere. It's ancient history, and didn't have half the features of v21.2. People will just dismiss you as a luddite, no matter what your arguments are. But onto the matter at hand...

I have a reasonably decent PC (core i7-9700k, 64GB RAM, GTX 980ti, M.2 SSDs) and I concur that this update has absolutely tanked my performance. In my multiple-artboard PSDs, Photoshop has become borderline unusuable. I'm really hoping a new Nvidia update or PS update will fix this, as it's a serious problem for me.

I also agree with the OP's sentiment that you should prioritise performance and smooth running over new features. There are fancy new niche features every major update which most of us won't ever use, yet the pile of bugs and performance issues slowly grows and grows. While the shell becomes ever shinier, Photoshop is slowly but surely eroding from the inside. 

I myself have some filed some 100% reproducible bug reports on this forum that are now literally years old, and get routinely ignored by Adobe year after year, while each major update seems to break something new. I'm getting tired of it. 
(Edited)
Photo of Jaroslav Bereza

Jaroslav Bereza

  • 952 Posts
  • 254 Reply Likes
I agree with niche features. Therefore I like to see that Adobe now invests huge effort into new extensibility so you would be able to opt-in 3rd party features or maybe even Adobe features and not bloat PS with something you don't need.
Photo of Johannes Radicke

Johannes Radicke

  • 2 Posts
  • 0 Reply Likes
I have the same issues as OP after the update. I am running the Macbook Pro 2020, 2,6 GHz 6-Core Intel Core i7, 32 GB Ram, AMD Radeon Pro 5500M 4 GB and my files with multiple artboards are a real struggle to work with now. Especially when trying to edit text or moving several layers... its a nightmare compared to before. How could this have happened? Hopefully a hotfix is coming asap.
Photo of Vlad Limer

Vlad Limer

  • 1 Post
  • 0 Reply Likes
same issue 
I7 6700K 64GB-ram  M,2-SSD 1080TI 11GB 
=\
I Cant Work with this new updates!
Photo of Jaroslav Bereza

Jaroslav Bereza

  • 952 Posts
  • 254 Reply Likes
It might be also a bit dependent on content. When I did web design in PS 2015.5 it had much better performance than PS2015 and even more than PS CS6. There were hundreds or thousands of small layers... mostly text and shapes. 
Photo of Giordano

Giordano

  • 28 Posts
  • 4 Reply Likes
Glad I haven't updated, still on 20.0.9 (CC2019) and despite being disappointed I cannot enjoy the wonderful new features of the new release yet, at least I can work..
Photo of Dave Grainger

Dave Grainger

  • 503 Posts
  • 95 Reply Likes
A ten year old PC with an I-5 processor and an old GPU! It is unreasonable to expect any software maker to continue support for "legacy" systems forever. This is not an Adobe update problem, it is your problem for not staying current with required specs. 

Trying to haul boulders with a garden cart never has worked for me!
(Edited)
Photo of Ed

Ed

  • 30 Posts
  • 3 Reply Likes
Don't tell me my hardware is old, because I'm talking about software performance and you're no Software Engineer brother. This message isn't for you anyway, it's for Adobe's developers.

Facts are there !
Photoshop's running performance was degraded by the new features that have been implemented. Implementing new features in a software is in no way synomym of degrading performance. The user with the old hardware will only use old features that remained in a software. Else there would be a software quality problem.
In our case, it's about painting tools and rendering performance with the same old tools that are in the new release of the software.
Testing Photoshop CS6 and comparing it to the current Photoshop CC allowed me to realize about some very bad flaws that Photoshop's developers didn't take care of. 
And by the way, Photoshop is NOT the only software upgrading on the market wth new technologies. Clip Studio is another software, Blender too. Sketchbook as well. Affinity Photo too. Krita is also there.

SO WHY ON EARTH performance degrades with the new Photoshop while it remains good and stable with other new painting/drawing softwares ? Yes because I test them too if you didn't know, sir Dave Grainger.

I'm too frustrated already and do not have enough money to upgrade my specs. So unless you can help me report this problem don't tell me anything I don't need. 
Thank you for understanding. 


Photo of Dave Grainger

Dave Grainger

  • 503 Posts
  • 95 Reply Likes
Ok, just keep on loading that garden cart....
Photo of David Bleja

David Bleja

  • 110 Posts
  • 58 Reply Likes
@Ed: I told you people would dismiss you as a luddite ;)

@Dave Grainger: something does seem funky with this update. I've got a pretty good PC. It's a couple of years old, but most of the gear was top-end: i7-9700k, GTX980ti (x2 in SLI) with 6GB VRAM, 64gb-2133 RAM. Photoshop is installed on a top of the line Samsung m.2 SSD, while the scratch disk is on a separate, dedicated SSD. 

Yet this update tanked my performance enormously. The files I was happily working on last week became basically unusuable this week - despite nothing much changing in the feature set. 
(Edited)
Photo of Dave Grainger

Dave Grainger

  • 503 Posts
  • 95 Reply Likes
David Bleja: That is a pretty powerful machine indeed, with one question. That video card dates from   June 2, 2015 (GeForce GTX 980 Ti). Perhaps it is the problem? Or, drivers need updating...
Photo of PECourtejoie

PECourtejoie, Champion

  • 906 Posts
  • 337 Reply Likes
David, are you also using Wintab? Which function exactly is slower for you?
How does it work on Windows INK?
Photo of David Bleja

David Bleja

  • 110 Posts
  • 58 Reply Likes
Dave: Yes, it's an ageing card, but it's from nvidia's top price bracket - those cards tend to still outperform mid- and low-range cards from the next generation or two. Yes, drivers are up to date.

As I mentioned, the performance was fine on 21.1.3 but tanked with 21.2, even though 21.2 appears to have added only peripheral features rather than overhauling core infrastructure. Similar things seem to have happened for others. 

And, for me at least, some of the extra slowdown is caused by the new extra thick grid, which according to Jeffrey isn't even supposed to be there. So there's definitely something not quite right with this update. 

PECoutejoie: If I understand your question, the implication is that my tablet driver might be causing problems, yes? I own a wacom and have it plugged in, but don't actually use it nowadays - I use the mouse. I hadn't heard of Wintab so probably don't have it. However, maybe you're on to something and the wacom drivers are partly to blame here. It wouldn't surprise me, as I've had multiple problems with wacom drivers over the years. I'll disconnect and uninstall the wacom, reinstall 21.2, and report back.
Photo of David Bleja

David Bleja

  • 110 Posts
  • 58 Reply Likes
Updated my wacom drivers - didn't seem to make any difference. Uninstalled the drivers completely - maybe that made a little bit of difference. It seems usable now when the grid is off, though a slideshow when the grid is on. 
Photo of Austin Branham

Austin Branham

  • 5 Posts
  • 14 Reply Likes
This version has destroyed my performance and I'm on a 10 core iMac Pro with a Radeon Pro Vega 64 16 GB graphics card. I'm not sure what happens - everything will be running smoothly, and then I try to use the type tool and it starts to lag and artboard turns grey.
Photo of Johannes Radicke

Johannes Radicke

  • 2 Posts
  • 0 Reply Likes
+1
Photo of Dave Grainger

Dave Grainger

  • 503 Posts
  • 95 Reply Likes
Your [Austin] video is also older: August 14, 2017. Same comments about updating the drivers and/or the video circuit...
Photo of Austin Branham

Austin Branham

  • 5 Posts
  • 14 Reply Likes
@dave, no its certainly not the video card. The Pro Vega 64 with 16GB combined with 128GB ram has been pretty powerful for me. I do tons of 3d animation work, and the old and new versions of AE work perfectly for me. The old PS worked perfectly just two days ago before updating. That's all that needs to be known.

The problem lies in the software, not the hardware.
(Edited)
Photo of Dave Grainger

Dave Grainger

  • 503 Posts
  • 95 Reply Likes
Austin: I agree that you have a powerful card. My point was that, since it is a few years older, there may be driver issues between it and the updated PS. Reading through the other threads on this forum, I have seen a lot of that sort of thing. Just because it is  a very nice card does not mean that you should not update the SOFTWARE drivers for it...   BTW, you actually have a more powerful machine than my current one!
(Edited)
Photo of PECourtejoie

PECourtejoie, Champion

  • 906 Posts
  • 337 Reply Likes
Ed, did you try to use Windows ink?
Photo of Ed

Ed

  • 30 Posts
  • 3 Reply Likes
Yes I tried to use Windows Ink. But the Modifier Key pop-up is annoying plus some operations are inconsistent with it :

-selecting a layer and clicking on a layer group with your pen/stylus to open/close it, there are operations failures unless you click in a tricky way or click rapidly multiples times;

-Color picking has a very brief input delay before execution with Windows Ink, making it slower in function than color picking with Wintab;

-The Modifier Key popup utterly annoys me and appears everytime I press on any of the corresponding keys.

From the very first Photoshop CC, while brush strokes precision were improved with Wintab, a single stroke performs slower and slower the more you hold your pen press without committing your brush stroke(performance issue unseen from Adobe for years). As a result, brush strokes with Windows Ink became faster than brush strokes with Wintab since PS CC 2014 or the very first Photoshop CC if you want. This does not solve however the stuttering, wintab performance issue with Photoshop CC, fps decrease overall, and other performance related issues with the current version of the software. If you can, please, stop adding new features and focus on software optimization from now. And don't leave support for wintab until your fixed one last issue in its implementation.

Now, you probably do not have time, but for the sake of the quality of your softwares, do even more tests as your optimize your programs, and compare your apps performance to the performance of some other popular softwares of the same niche(including Krita, Clip Studio Paint, Medibang Paint Pro, Autodesk Sketchbook), and do this on machines of all kinds of generations, from older gen low-pecs to last gen high-specs. Hire people to help if needed. 

I have spoken. The ball's in your court now.
Photo of eartho

eartho, Champion

  • 1537 Posts
  • 533 Reply Likes
I'm also seeing quite a bit of stuttering across all Adobe apps when using Nvidia Gsync. No issues in any other apps, only Adobe.
Photo of adam temp

adam temp

  • 15 Posts
  • 14 Reply Likes
Hello,
The cc support told me to come here. 

For the past few versions of PS I've noticed an increased slow down on simple thing like making shapes and pen points. 2020 was the straw that broke the camels back. 

What I've tried: 
Clearing profiles
going through the graphics acceleration settings
going through ps advanced adjustment page
making another new window profile with admin privileges
moving cache drives around
removed all plugins
made sure all drivers are updated
Switched on and off the legacy options

Pretty sure it's on adobes end at this point

System: 
win 10 ryzen 8 
32 gigs of ddr4 3400
gtx 1080ti
1 ssd for programs
1 1tb cache drive

There is are multiple threads on the main community channels with hundreds of posts about PS slowness that no one from adobe has acknowledged here is one of them: https://community.adobe.com/t5/photoshop/photoshop-2020-running-slow/m-p/11251528?page=1#M344045

So far the consensus has been to go back to 2018/2019 when the slowness is manageable or just go and buy affinity photo for its speed. 

Here is a video about just one part of how slow it's become: 

https://www.youtube.com/watch?v=-DJrn2ICxUo&feature=youtu.be




  
Photo of eartho

eartho, Champion

  • 1529 Posts
  • 527 Reply Likes
and you definitely tried enabling the Legacy Compositing pref? 
I tested the same tools you did on a 2K canvas which was already populated by about 100 placed smart objects and didn't see any performance issues like yours. I wonder if the ryzen is the culprit?
Are you keeping an eye on your VRAM usage in the Task Manager? Sometimes when that gets full, everything in Ps will grind to a halt.
Photo of Dave Grainger

Dave Grainger

  • 495 Posts
  • 92 Reply Likes
" I wonder if the ryzen is the culprit?
Are you keeping an eye on your VRAM usage in the Task Manager? Sometimes when that gets full, everything in Ps will grind to a halt."

I think that is very likely what is going on.... 
Photo of Rick O'Dell

Rick O'Dell

  • 4 Posts
  • 6 Reply Likes
Stop attempting futile and unnecessary work arounds on this. It is noone's fault, nor the computers fault, that the program doesn't work as it should... This is 100% on photoshop. 
Photo of adam temp

adam temp

  • 15 Posts
  • 14 Reply Likes
 yes I tried legacy. Vram never goes past 2% just making shapes, I have 12 gigs of vram. 

Also if you see the link to the thread you can see both mac and windows users are experiencing this so i doubt it's my cpu. 
Photo of Rick O'Dell

Rick O'Dell

  • 4 Posts
  • 6 Reply Likes
Dave... you don't sound like a daily user. Adam, I agree with you. We should not have to rebuild or clean our entire Windows or Mac over a simple update. Hence, simply reverting back to previous photoshop version works just fine.
Photo of Dave Grainger

Dave Grainger

  • 495 Posts
  • 92 Reply Likes
Since the first edition of Photoshop...
Photo of David Bleja

David Bleja

  • 110 Posts
  • 58 Reply Likes
They're right, Dave. I've seen quite a few posts from you now essentially offering the same thing for various circumstances:

-'maybe the Ryzen is the culprit'?
-'maybe your GPU is the culprit'?
-'maybe your drivers are the culprit'?
-etc.

They're ostensibly fair enough questions, but with each post it should become increasingly obvious that those stabbing-in-the-dark theories effectively cancel each other out. What's the common denominator between all of these situations? It's not the CPU, it's not the GPU, it's not even MacOS or Windows. The common denominator is Photoshop 21.2.

I know you're just trying to help, but ultimately your attempt to help comes across as incessant and baseless skepticism, whether you intend it this way or not. 

Some unintended flaw in 21.2 is crippling Photoshop for a great many people - in many cases the result is a drastic overnight loss of performance. The number of reports are far too numerous and varied to be a coincidence. I'm sure Adobe is taking notice, and they'll probably fix things eventually.

Users are understandably frustrated when they come here to report the problem. So when a user who's lucky enough to be spared similar problems basically says 'it's probably your fault' to anyone and everyone who reports similar problems, it starts to get grating. 
(Edited)
Photo of Abi WoodBriDGE

Abi WoodBriDGE

  • 2 Posts
  • 2 Reply Likes
This observation by D. Bleja is Spot ON!  Trying to defend ADOBE by suggesting every possible tweak of every computer in the world >>> is not dealing with the reality of the issues.  THIS IS ADOBE at fault.  Unfortunately 'eventually' fixing it means we keep paying for the subscription and the privilege of wasting our time attempting work arounds. 

An Adobe Tech moved me back to PS 20.0.8 and now Bridge is acting up AGAIN!  When I tweak BRIDGE to work correctly, then PS breaks down.    See Timur D's  comment about the GPU getting disabled.  That lurching and choppyness etc., sure is like what's going on in my machine.  And Rick O'Dell and Adam T.'s observations... AND EVERYONE ELSE! 
Photo of Timur Dzhambinov

Timur Dzhambinov

  • 3 Posts
  • 12 Reply Likes
It's like GPU gets disabled after 5-10 minutes of working. Zoom is choppy, antialiasing switches off, performance is terrible. Tested on 2 separate macbook pros. Rolled back to 21.1.3, thanks Adobe! Good testing..
Photo of Rick O'Dell

Rick O'Dell

  • 4 Posts
  • 6 Reply Likes
I am joining the crowd with lagging problems in the latest versions of Photoshop. I eventually had to revert back to 2019's latest update, which works just fine. For anyone looking for a fix or workaround, there are no solutions to this problem from our end. They have all been attempted. So don't keep trying. Just uninstall the latest updates (anything in 2020), and revert back to 2019 and you will be back to work.

BTW, I have an extremely powerful machine, bought brand new in 2019 with about as much speed/ram/memory/graphics card etc one can pile into one machine. Aprox $2000 total spent on it. I am a professional graphic designer going on 20+ years.

As for specifics?... ie lagging, sluggish, glitching, blackouts, whiteouts, etc etc. Previous comments in this thread say most of it, as well as this link through Adobe's support forum: 

https://community.adobe.com/t5/photoshop/photoshop-2020-running-slow/m-p/11255888?page=14#M344529

... where hundreds have experienced the same thing. There has been talk in the forum linked about getting an attorney involved if anyone would like to team up. Since we are forced into paying a monthly subscription, we are forced into paying for a product we cannot use. We are currently openly and unashamedly being swindled. I've paid my monthly subscription, I would like a new and updated version that works. The problems first arose very beginning of 2020, and as you can see, they have made zero effort to patch or fix. We are being robbed. 
Photo of David Bleja

David Bleja

  • 109 Posts
  • 57 Reply Likes
Hi Rick, can you confirm which version is working well for you? I want to revert too, but I'm a bit confused because Adobe used to (or still do?) add years to their product names, so I'm not sure what you mean by "back to 2019" - a version released last year, or a version that's actually called CC2019.

When you say "back to 2019", do you mean 21.0 (released in Nov 2019)? I noticed that near the beginning of that thread you posted, people were complaining about the November version, and saying to go back to CC2019 (which I guess was released earlier in 2019? Or maybe 2018?). 

I've experienced a momumental performance drop with 21.2 in particular, but like others I've also noticed a slow gradual decrease over the past year or so. So I'm keen to find an older version that works ok and stick with it until this whole mess is eventually sorted out. Which, knowing Adobe, will take years, not months. 
(Edited)
Photo of Giordano

Giordano

  • 27 Posts
  • 4 Reply Likes
I guess it's 20.0.9, which is the one I reverted to and it's working fine (I'm on windows 10).


(I really wish Adobe decides to sell that version as a separate product so that I can stick with it without worrying for future updates)
Photo of David Bleja

David Bleja

  • 109 Posts
  • 57 Reply Likes
Thanks. I ended up figuring that was the case, and I've just reverted to 20.0.9.  All I can say is....WOW! It's like driving a Ferrari! I'd actually forgotten that Photoshop used to be this fast. It's like getting to experience some wonderful future version of Photoshop, except it's from the past XD

I can't believe I'm going to be paying monthly subscription fees for a service that stopped working properly over a year ago...
Photo of Giordano

Giordano

  • 27 Posts
  • 4 Reply Likes
Exactly, I had the same feeling.
Adobe should reconsider selling standalone licenses (not cc) of fully functional products, and leave the creative cloud for the audacious (or the fan boy..)
Photo of David Bleja

David Bleja

  • 109 Posts
  • 57 Reply Likes
I've been a supporter of the Creative Cloud model since day one. I like not having to pay thousands of dollars up-front, and I like getting new features and updates automatically. 

But I'm reconsidering my position now for sure.

New features they've added over recent years like (artboards, better vector tools, better layer styles, generator auto-export etc.) are indispensible to my workflow now. I wouldn't go back to CS6 for any money. 

But I've also been waiting for literally years for Adobe to fix some really basic bugs and glitches that remain untouched in version after version. Meanwhile, the updates just seem to break more stuff than they fix. Just what exactly am I paying for with these monthly payments? 
(Edited)
Photo of Rick O'Dell

Rick O'Dell

  • 4 Posts
  • 6 Reply Likes
You bet David. I actually am having good luck with 21.1 currently. It was 21.2 that almost lost me some clients. Reverted back to 21.1 overnight to get projects done the next day. 20.0.9 was even better. 
Photo of David Bleja

David Bleja

  • 109 Posts
  • 57 Reply Likes
Hmm. I'm surprised 21.1 works well for you, as that's the one that adds the "Performance Improvements", which I assumed were (ironically) the culprit behind a lot of these performance problems. 

I might try 21.0 myself, as I liked the improved preset system it included. 
Photo of Dave Grainger

Dave Grainger

  • 503 Posts
  • 95 Reply Likes
Beginning to sound like Bastille Day!
Photo of Dave Grainger

Dave Grainger

  • 503 Posts
  • 95 Reply Likes
Rick O'Dell: You do not have an actionable claim without injury or loss of functionality; your subscription allowed you to rollback to an earlier version and therefore Adobe is not in breach of any contract. Nobody has "forced" you to do anything; you are free to continue using the prior product or to take your bat and ball to another playground at any time. You also have zero inside information about whether Adobe is working to discover a fix or not.



It is a sad commentary on these later generations, the entitlement generations, that when one does not get what they want, there is first a tantrum followed by immediate escalation to legal action!
(Edited)
Photo of Austin Branham

Austin Branham

  • 5 Posts
  • 14 Reply Likes
I feel like this guys works for Adobe or something lol. Defending an update that is clearly causing trouble for the masses. As I said earlier, it is not the cpu, it's photoshop. 

This is not a matter of "getting what one wants". Adobe does not make their apps simply for their own use. It is for us, the consumers. When the entire consumer base raises concerns, clearly the producer needs to respond and try to make things right.
Photo of adam temp

adam temp

  • 15 Posts
  • 14 Reply Likes
didn't they pull the older installs from CC and you can only go back to 2019 unless you go to some weird third party page,  that's how I had to get 2018. 

Why yes he has no claim but this is really bad marketing and product launch. But then again it's par for the course for a company that never really fixes any of the older issues or advances their software appropriately.  Just look at the 20 years garbage pile of after effect, animate, dreamweaver and AI.
I grind my teeth when I have to open them up, just old crap with bad UX that people have to use because of legacy client stuff. 

Photo of Dave Grainger

Dave Grainger

  • 503 Posts
  • 95 Reply Likes
Not defending the update, just criticizing the complaining and bitching and people threatening legal actions that are serving no purpose and do not contribute to the solutions, which WILL come.
Photo of Timur Dzhambinov

Timur Dzhambinov

  • 3 Posts
  • 12 Reply Likes
not for legal action in this case, but i'm not sure about the "solutions will come" part. Smart objects still make huge empty layers, performance sucks, I still get weird bugs exporting artboards etc etc. Tested and replicated on 3 separate machines (2 macbook pros, 1 windows machine).

I lost faith in adobe personally. Unfortunately, my agency is not quite in with the time and wants us to use creative cloud apps..
Photo of Dave Grainger

Dave Grainger

  • 503 Posts
  • 95 Reply Likes
Granted this update was a "mell of a hess" but since I do not work for Adobe, I have no idea how much time will be required to unring that bell and make it all work again.

Any business, in order to continue to exist, must get and retain customers by delivering goods and services that (1) are perceived as having value by those customers, and (2) that actually do work as promised. Dissatisfied customers vote with their checkbook, go to competition when they do not successfully meet (1) & (2). In addition, the company must manage itself well enough to generate profit to pay employees, pay investors, pay suppliers. Failing that COULD be caused by serious error in paying attention to (1) & (2).

So, Pissed Off Posters take note: there is no way that Adobe could possibly be ignoring this debacle nor could they have created it intentionally. We all can be assured that there is serious mid-night oil being burnt in effort to get this behind them as quickly as possible.
(Edited)
Photo of Timur Dzhambinov

Timur Dzhambinov

  • 3 Posts
  • 12 Reply Likes
There are issues that haven't been addressed for ages.
Photo of Ryan Terry

Ryan Terry

  • 3 Posts
  • 4 Reply Likes
just criticizing the complaining and bitching
What a delightfully pointless way to use the internet.

Do you honestly believe anyone places any value in your opinion when all you've done throughout this thread is desperately attempt (and ultimately fail) to invalidate the opinions of others? Why would they? Your opinion, even if taken seriously (which is very difficult, given how obvious it seems that you have a vested interest in Adobe [e.g. I'd bet you work for them]), is of no consequence.
Photo of Etienne Bugeja

Etienne Bugeja

  • 1 Post
  • 0 Reply Likes
Hi guys having major issues here too. I have a core i9, 64G Ram, 1080ti and everything running on ssds and nvme's. Update after update photoshop is getting worst. Slow and bloated with useless features. For me even saving and closing documents freezes for a couple of seconds. While sketching sometimes it freezes completly for no reason. I actually monitored my pc and there was nothing working at 100%. Then there is customer care. I spent 1hr chatting and all they did was pasting me links of steps for me to follow. After following all the steps nothing changed. The only solution I could find is reverting back to the oldest version I could find on the creative cloud. 

I have suggestion. I love the idea of having two versions of Lighroom. Why not apply the same idea for Photoshop. A version for professionals and a version for new comers. 

Photo of Dave Grainger

Dave Grainger

  • 467 Posts
  • 84 Reply Likes
Elements
Photo of mac xide

mac xide

  • 5 Posts
  • 4 Reply Likes
i think but now not have processor design for photoshop 
but 2050 you can use photoshop not slow 

Photoshop CC ++ Very Large and Very Slowly 

if you can use very fast you can get Photoshop CS 5.5 Version Only this is a Best Production made by Thomas knoll
Photo of Dave Grainger

Dave Grainger

  • 503 Posts
  • 95 Reply Likes
CS 5.5 was EOL back in 2018!!!
Photo of adam temp

adam temp

  • 15 Posts
  • 14 Reply Likes
To be fair, I think 5.5 was the best version step that ever came out, since then it seems like they keep adding features like stomping down a trash can. 
Photo of Dave Grainger

Dave Grainger

  • 503 Posts
  • 95 Reply Likes
I held on to CS6 until switching to CC2020 last year.  Let's face it: the world moves on regardless! Five point five has no chance of working with today's hardware and OS.

Your choices really are (1) Restore your computer to a Restore Point predating Windows last Update, and keep it OFF of the internet, else Microsoft will jam the update through again, or (2) get CC2020 and learn how to use it (I can give you links to get very good training), or (3) get a different program.  That will be quite hard to do, as everything out there has moved on past what you are using.

Just curious: what is the primary use for Photoshop for you? Mine happens to be photo editing plus a limited amount of graphics and restoration...
Photo of Dave Grainger

Dave Grainger

  • 503 Posts
  • 95 Reply Likes
I intended this comment to be on a different thread...
Photo of adam temp

adam temp

  • 15 Posts
  • 14 Reply Likes
I'm a freelance media artist. 

I handle pre and post-production asset needs for various types of campaigns for clients in advertising and video games. 

PS 2020 is crap, I moved back to 2018 and also bought affinity photo for the enhanced speed all my new clients are getting worked on outside of the cloud, I'm hoping to drop it by the end of the year and only purchase it on a client needs, I really think Adobe is screwing the customers at this point
Photo of David Bleja

David Bleja

  • 110 Posts
  • 58 Reply Likes
Some kind of response from someone who works at Adobe would be nice. I don't know how much a chunk of a userbase is suffering from these new performance issues, but judging from this and other threads it's clearly more than just a handful of individuals.

And just to hammer the point again: for at least a portion of us, the performance problems brought on by the latest patches are horrific. We're not talking about hiccups or occasional freezes, we're talking about simple operations becoming grindingly, inexplicably, show-stoppingly slow. 
Photo of Anthony Edge

Anthony Edge

  • 119 Posts
  • 35 Reply Likes
I think you'll find that many users have just rolled back to earlier versions, or never installed the updates to begin with. They are so often a waste of time and none of the included features are crucial. How could we possible wait for fixes to this train wreck. There's not even a proposed patch date!

But it's not like Adobe release upcoming feature lists which promise to optimise all your workflows and increase efficiency with performance enhancements and features. Can you imagine selling work to clients in advance, based on upcoming Adobe feature inclusions? It's laughable how doomed such activity would be given Adobe's track record.

The simple fact is, early adopters are Adobe's test team. Congratulations, you're one of them. Only you don't get paid, you get no communication or praise, you're a slave.

They release garbage, we become guinea pigs. Repeat. 
Photo of Abi WoodBriDGE

Abi WoodBriDGE

  • 2 Posts
  • 2 Reply Likes
OMG!   I nearly fell off my desk chair laughing:  Sweeek weeek weeek weeek weeek weeek.

On the count of three, all little piggies out there lift your faces up out of the wood chips, drop your carrots & veggies and:

Raise your squeaky voices high and in Resounding Chorus... proclaim your heartfelt confidence that Adobe will engage in a PUBLIC, FORTHRIGHT, ADMITTANCE OF FAILURE in cleaning out the dross, bugs & glich in PS & BR and that it will announce the complete elimination of it's Excuses Department while simultaneously developing a functioning Rebuild Team whose motto shall be: "We Build it - It's Broken - We Fix it - NO EXCUSES - EVER".

Since that's rather unlikely to occur because the investors are making too much money and the techs et alia have job security (so why change)... Instead,  lets just sing to Adobe's adroitness in dodging responsibility and of its heavyweight corporate incompetence in discerning that it has completely failed in mastering that fine art of ingenuity & GETTING IT DONE for the customer's sake.









Photo of Helen Slater

Helen Slater

  • 1 Post
  • 0 Reply Likes
When I switched off Use Graphics Processor under the Performance tab in Preferences it really helped.
Photo of adam temp

adam temp

  • 15 Posts
  • 14 Reply Likes
You do realize that when you turn that off you lose areas of the program, like rotating your canvas and several effects
Photo of dandi wind

dandi wind

  • 10 Posts
  • 4 Reply Likes
It's just a temporary workaround until Adobe fixes this huge issue
Photo of mac xide

mac xide

  • 5 Posts
  • 4 Reply Likes
If you want to use this version you wait about 15++ year's to use 
but now processor unit , and gpu card unsupported