Participant

Answered

Photoshop CC -> performance down, memory usage up.

Forum|Forum|12 years ago
June 27, 2013
42 replies
138113 views

I recently switched to Photoshop CC.

I noticed performance was slow, memory usage was huge. At first I thought it might be because I was processing somewhat larger panoramas than previous ( eg merging 25 images at 21 MP each ).

Then my SSD drive crashed when the sysem ran out of memory, and I can't recover it.

I reinstalled Mac OSX 10.7.5 on the original HD and re-installed PS. Now my network bandwidth has jumped from under 1 GB uploaded per day, to 20GB, 30GB, 44 GB uploaded.

I don't know how much of this can be traced to PS CC, other than it's slow performance and high memory usage, but it' a suspicious coincidence.

Tom Legrady

This topic has been closed for replies.

Correct answer Chris Cox

That would be because the memory usage is about the same as previous versions, and we don't know of any major memory leaks in Photoshop CC (we do a lot of testing to find and eliminate memory leaks in Photoshop).

And because we've seen third party drivers and third party plugins with memory leaks.

If Photoshop consumes that much RAM without opening any documents - then you have about 6 Gigs of presets being loaded at launch (which is presets that you added, because by default Photoshop doesn't load that many presets, and consumes under 300 Meg at launch).

If you mean that Photoshop cosumes that much after closing documents - then that is how much you allocated to Photoshop and used in your documents. Photoshop not releasing memory back to the system until exit is perfectly normal behavior (otherwise it would run much slower).

We can try to help you determine what is consuming memory on your system.

But insisting that Photoshop is the cause when it is easily verified as not being the cause, won't help you.

Show previous replies

O

orion128

Participating Frequently

I updated my CC version of Photoshop, for Photoshop CC 2014 version.

Now I work a lot slower than the previous version, so I can not nomally work. Moving objects, loading the editing tools, zoom, and scrolling is much slower. I do not understand why, in the previous version everything was working properly.

I have the following configuration:

Windows 7 Pro 64bit
Gainward GeForce GTX 770 Phantom 4GB

Intel i7 CPU

16 GB of RAM

Mpower MSI Z77 motherboard

My PS performance settings:

PS The use of 70% of RAM

3 scratchdisk with 250GB of free space

4 catche levels

Can you help me to solve the problem?

C

chuck@chuckespinoza.com

Participating Frequently

Despite paying a monthly fee for CC I gave up using it. For the adobe techs to say that there is nothing wrong is a joke.

I am running a six-core system with 32 GB ram, an SSD, an empty drive dedicated to cache, on a win 7 - 64bit OS. Bridge, camera raw and Photoshop CC are so slow I can't use them. To tell me that nothing has changed between CS6 and CC is a lie or the person making the statement doesn't have enough information to make that blanket statement. With each new upgrade (including this week's) I try to use CC only to put it away and use CS6 again.

Like our counterparts with lightroom I often batch edit raw file files in camera RAW. I tried to grab canon 5d Mark III files and I got an hourglass. In CS6 there isn't any delay. Switching between folders in bridge takes forever (even if the cache is loaded).

there is an issue

Chris Cox

Legend

Millions of other users are not seeing any such slowdown. We cannot reproduce any such slowdown.

We have lots of information, but all of it tells us that the problem is something local to your system.

C

chuck@chuckespinoza.com

Participating Frequently

Are you or adobe offering custom tech support to go along with my monthly payment?

I am running CC out of the box? Just like the update I installed last night. I have increased the ram usage in my photoshop preferences but that has no effect on camera RAW nor bridge

R

rtl300

Participant

It is a sad state of affairs when the official response to all of these concerns about memory usage is 'it's your fault not ours'. I've upgraded photoshop through each version from photoshop 7 and have never faced the issues that are occurring with CC. If third party plugins and drivers affect Photoshop that badly then surely they should affect CS5 in the same way as they are affecting CC but I can assure you that my CS5 works perfectly and CC is unusable. I, as many others in this discussion, feel that this is most certainly an issue for Adobe to solve, as long time Adobe users and supporters we deserve better service than this. I am only able to use the RAW conversion element to CC (because CS5's version hasn't been updated to convert Nikon D600 or 800 RAW files) and once my tiffs or jpegs have been generated I then have to shut down CC and load up CS5 to work on them, I shouldn't be paying a monthly subscription to do that!

D

Dustin07

Participating Frequently

The fact that these techs are going to tell every single person that the problem with the memory being eaten up by photoshop CC is in their systems.
The fact that these techs are going to keep telling people that the memory usage is the same as previous versions of Photoshop.
I restored the latest version 17" model Macbook pro to its factory settings and replaced 8 gigs of ram with 16gigs and then did a new install of CC and I have to tell you that even if you set the preferences to 30% in Photoshop, it still eats 6 gigs without a document opened! th bottom line is the more RAM addeed the more it takes. I have been reading these posts since I subscribed to CC 4 months ago and nothing has changed. The Adobe specialists tell everyone that it is their system that is the problem and Photoshop is the same as it has always been. Well I am sorry but, I find this unacceptable. I am seriously thinking about getting rid of my CC membership because of what is happening. To me the difference between CC and CS5 is small. Content Aware is the same to me whether it is CS5 or CC. It is just sad that instead of finding a solution to this problem it is being denied instead. The fact is, we all need Adobe software because there is no other alternative so, we are at the mercy of those who tell us that the problem lies in our systems.

Chris CoxCorrect answer

Legend

That would be because the memory usage is about the same as previous versions, and we don't know of any major memory leaks in Photoshop CC (we do a lot of testing to find and eliminate memory leaks in Photoshop).

And because we've seen third party drivers and third party plugins with memory leaks.

If Photoshop consumes that much RAM without opening any documents - then you have about 6 Gigs of presets being loaded at launch (which is presets that you added, because by default Photoshop doesn't load that many presets, and consumes under 300 Meg at launch).

If you mean that Photoshop cosumes that much after closing documents - then that is how much you allocated to Photoshop and used in your documents. Photoshop not releasing memory back to the system until exit is perfectly normal behavior (otherwise it would run much slower).

We can try to help you determine what is consuming memory on your system.

But insisting that Photoshop is the cause when it is easily verified as not being the cause, won't help you.

Chris Cox

Legend

The Adobe denial is just stunning. I have watched Photoshop behave erratically and consume MUCH more memory than usual on many occasions. If it always behaved this way then it would be working as Adobe intended, but that is not the case.

Most of the time when I run Photoshop it uses under 25,000 K of RAM when no files are open. This allows me to multitask and use other programs, such as Lightroom, without having to shut down Photoshop to free up memory. I almost always keep task manager and CleanMem Mini Monitor open, so I can both see what is consuming memory and free up that memory when a program goes out of line.

Tonight I opened Photoshop CC in anticipation of working on a few files, since launching Photoshop cold from Lightroom is hit or miss, and everything went South. Lightroom jumped to 1,598,844 K and Photoshop jumped to 4,843,380 K. I often have Photoshop use around 10 Gb of RAM when I am editing photos, but this is unusual from the start. I could not get the RAM to clear, and I was getting insanely frustrated, but using that much RAM is not a deal breaker since I have plenty.

I was able to get the problem to resolve itself by opening up 5 30 Mb Raw files and a 200+Mb PSD and doing some quick edits on them. By the time I had closed all but one of the CR2s I was using just shy of 1 Gb of RAM and Photoshop was running like clockwork. When I saved and closed out that final file Photoshop dropped down to its' usual 24,652 K, and Lightroom had dropped back down to 65,452.

So, is this Photoshop "working as usual?" You cannot tell me that Photoshop is supposed to grab almost 5 Gb of RAM that it does not need when I first open it, causing it to be sluggish and slow down the rest of my system, only to give it up and run smoothly after I have used it for a bit. When Photoshop is not hogging all of my memory it runs just fine, and I can keep it open all day, even when not using it, without noticing any drain on my system. THAT seems to be working as intended. It is when it is working right that it uses memory when it needs it and does not use memory when it does not.

I, like hundreds or thousands of others, have arrived at this thread because Photoshop suddenly started behaving badly, hogging RAM, and IT DID NOT DO IT BEFORE! I am not talking about CS5 or CS6, I am talking about YESTERDAY with CC. Nothing on the system has changed, I have over 350 Gb free on my system drive, Photoshop just suddenly started behaving different.

I am not writing this, angry as hell, because the program is horrible or because the problem it is not something that I can work around most of the time when I need to, what ticks me off are all of the "Staff" members that are saying "Move along, nothing to see here, it is just your system. . . . Did you try turning it off and on again?" or the dreaded "Photoshop has always done that, you just did not notice." Sorry Bub, but the reason that thousands of people come to this thread are because they DID notice, and they noticed something DIFFERENT! You can say "But insisting that Photoshop is the cause when it is easily verified as not being the cause, won't help you." is insulting for 2 reasons. 1. You are not taking peoples problems seriously, and you are talking down to them as though they are idiots for thinking that they have a problem in the first place, and 2. It is NOT easily verified because you have no idea what is going on. When I have a perfectly capable computer that is having no problems with any other software, and when tons of people come to you with the same problem of Photoshop behaving in a manner that it did not used to, you cannot tell me that you can verify that it cannot be Photoshop. You simply will not entertain the idea, and just because you will not consider that it might actually be a problem with the program does not actually mean that it is not a problem with the program.

Sorry for coming across as disrespectful, but frankly I am not being 1/10th as disrespectful as the "staff" on this board, and I am actually a consumer of your product, not someone that is supposed to be providing customer service.

Adobe has researched these slowdown issues, and fixed every one we can reproduce. But many of the issues only happen on specific systems, and frequently get tracked down to something specific about that system outside of Photoshop itself (antivirus, firewall, bad drives, bad drivers, other applications messing with the OS, etc.).

If Photoshop is grabbing RAM, it is because it does need it for something that you opened. That could be a document, or it could be presets that you have loaded. By default, Photoshop does not use that much RAM. And Photoshop won't use that much RAM until you load or do something that needs that much RAM.

Yes, even if no files are open, Photoshop will hold onto the RAM it has allocated - because it is MUCH, MUCH faster for Photoshop to manage it's RAM than to deallocate it and wait for the OS to reallocate it. (this is a pattern you will find in most applications that use a lot of RAM, including video and imaging applications and databases) There is no need to shutdown Photoshop to free memory - the memory it has will be reused for whatever you load or do next. Photoshop will also free memory if the OS needs additional memory (due to paging or hints). Photoshop has used the same memory management since version 2.0.

If Photoshop's memory usage is slowing down your system somehow, then you may need more RAM for the work that you are doing. Or you may have some other applications that are not managing their own RAM usage very well.

Now, we have seen some third party plugins that have memory leaks - and those are beyond our control.

But we test Photoshop rather heavily for memory leaks, and fix them rapidly.

R

rtl300

Participant

I've just 'upgraded' to Adobe CC purely because CS5 hadn't been updated by Adobe to open the new RAW files produced by my Nikon D600. Naturally as I'm paying for the new version I have tried to use it but it runs amazingly slowly even though it is all set to run as CS5 was and I have sadly had to revert to CS5 for everything other than RAW processing. Actions that run in CS5 without issue are laboured and slow in CC and after very little time a message simply appears saying that it can't function as there isn't enough RAM, something that hasn't ever happened with CS5. Very disappointed to be spending out on the cloud for a product that doesn't work. Have looked at Lightroom as an alternative but flaws in its layout and work processes mean I find it far more unsuited to RAW conversion than using CC or CS5...please get this memory usage problem solved!!!

A

Aspeeder

Participant

I recently "upgraded?" to CC at my office. I mainly use Photoshop and Dreamweaver. I have noticed a huge reduction in responsiveness. I work on a less than 1-year-old iMac, and since upgrading it take 5 minutes or more to open files that use to be relatively quick to open. I also am having slow save times. Just to manipulate text in a text box, sometimes causes the spinning color wheel to come op for 10 or more seconds. This kind of slowdown is affecting my productivity. What can I check to speed up my load times?

M

mmgulati

Participant

I have the same story with Adobe CC. I have Adobe CS5.5 on one system and CC on another. The file is ±400MB in size, and the CS5.5 uses 6-8GB of RAM while working on the file, while the CC uses 13-16GB of RAM on the same file.

Both systems have 16GB RAM installed, and are allowing Photoshop to use up to 90%.

I'm currently using 6 Cache levels and 1024 tile size.

B

booey

Participant

Yes, this is ridiculous. I was having some relatively minor issues with Bridge CS6 but am now on a different subscription and decided to switch to Bridge CC and Photoshop CC. Big Mistake. Pretty much made the problems worse and PS takes forever to load and open photos from Bridge. I just doubled my RAM to three weeks ago and now it looks like I will be needing even more of it. Adobe needs to get their act together.

Chris Cox

Legend

If Photoshop is taking more than 20 seconds to load... something is wrong with your system.

(and 20 seconds is on the worst laptop we can still boot, normal launch is under 7, and with an SSD it's under 2 seconds)

wendym97311974

Participant

‌i am having the same probleM with PS CC taking 5GB RAM and 12minutes to load. I am about to go in and delete all my presets as I'm desperate to get some work done.

A

Atsushi Hashimoto

Participating Frequently

I have same problem on Mac.

After closing my documents without quiting the app,

memory usage does not decreace.

I try to confirm with cleanning the histories and clipboard,

but the usage did not changed.

It occurs every time.

I don't use any plug-ins.

Chris Cox

Legend

That's not a problem -- memory usage is not supposed to decrease when you close documents.

Photoshop allocates memory up to the limit you set in preferences, then reuses that memory.

Photoshop won't release the memory until the OS needs it (paging), or you exit photoshop.

A

Atsushi Hashimoto

Participating Frequently

@Chris

No.

On my machine, PhotoshopCC eats huge memory compared with lower versions,

it doesn't release after closing docs. And my machine become very very slow.

CS6 and CS5 don't show this problem on same PSD.

Noel Carboni

Legend

I vote coincidence - for me Photoshop CC is just as fast as and uses the same number of resources as Photoshop CS6.

-Noel

M

MatthewPWright

Participating Frequently

I'm having a very similar problem. Since switching to photoshop CC I can no longer successfuly edit multiple images as I was able to do in CS6.

I have a Mac Pro running 24GB of memory, yet I'm running out due to Photoshop hording memory. Upon launch, Photoshop CC was using circa 1GB of memory, having processed 7 120mb raw image files as tiffs, the memory being used by photoshop has increased to a whopping 11.81GB of memory. Surely this is an issue with Photoshop CC?

Trevor.Dennis

Community Expert

Matthew, I'm just wondering how much space you have on your OS drive, as per Chris's comment in the post before yours? In these days of SSDs for OS and program files, people do tend to run very short, and that might be especially true of they have just subscribed to the full Creative Cloud package (although the 12 apps I installed came to a lot less than 10Gb).

M

MatthewPWright

Participating Frequently

Hi Trevor

I've got about 80GB free on the boot drive so would be suprised if this is the issue. I think I've worked out the issue this morning whilst working on some wedding photos though - it appears that Photoshop CC is bagging all of the memory I've allocated to it, under the preferences. It is then swapping out between Active and Inactive memory threads.

This appears to be a different behaviour to CS6 which only appears to use the memory if needed, not store it as inactive. As a result, CC slows down the whole system meaning things like Lightroom, iTunes, Safari etc have less to play with.

Does anyone think that sounds plausible?

Show more replies

Sign up

To post, reply, or follow discussions, please sign in with your Adobe ID.

Sign in to Adobe Community

To post, reply, or follow discussions, please sign in with your Adobe ID.

Scanning file for viruses.

This file cannot be downloaded