Skip to main content
New Participant
June 27, 2013
Answered

Photoshop CC -> performance down, memory usage up.

  • June 27, 2013
  • 42 replies
  • 137885 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.

42 replies

alyshajane
New Participant
October 23, 2014

I had a similar problem with my installation - whenever I used the Type Tool, Photoshop was unresponsive. I changed the preferences, and under performance increased the memory usage and also gave Photoshop access to a second scratch disk. Bingo! Problem solved - I can now add text without aging a few years while I wait for Photoshop to respond! It was all in the settings! Sharing in case it helps someone else. 

fabiohosoi
Inspiring
October 11, 2014

facing the same problems here.

I don't have PS third party plugins.

I work as cinema photographer (DP), usually works processing huge sequences of DNG in the automate/batch. to generate the tiff sequence its taking almost the double of time I've spent with CS 5.5. AME works better than previous versions, as I would expect.

when I have a  big sequence (4000 files or more), sometimes the program crashes. to avoid this I'm restarting the photoshop and just then I use the automate/batch.

win 8, i7 2,4ghz , 16gb ram, 3 hds (ssd system, scratch and file with 7200 rpm).

New Participant
October 10, 2014

Both Photoshop CC and CC 2014 are memory monsters as I have discovered.

I occasionally work with large images and for the past month have been working on one large panorama of about 6Gb in size, a month because Photoshop CC 2014 is unbelievably slow as it keeps creating huge temp files with every single action I try to take.

To illustrate this I took three screenshots for the simple action of opening the file and saving it with a different name. You can see how much time it took from the clock in the lower right corner and also the temp file growing to a ridiculous size for one single action.

My computer is a new Asus N56VB, with 16Gb RAM. Photoshop has 10Gb RAM usage.

I set history states to one only and scratch disks to two - not that it matters in this case.

If you can't see the times, it took from 7.23 until 7.40 to simply save the file with a new name, during which time Photoshop wrote a further 16.5Gb of data to the already large 35Gb temp file it created upon image open.

This is only the tip of the iceberg, had I decided to merge any layers then that would have taken a further 16-20 minutes whilst more huge temp files are created.

I then closed Photoshop and reopened the image and tried to resize it from 300ppi to 240ppi. No sooner had I entered 2 into the Resolution box it than started creating a preview and would not allow me to do anything until it had finished creating a 2ppi preview 11 minutes later along with two temp files, one 67Gb and the other 993Mb.

I then tried a second time and cancelled the preview for each digit entered until I had the 240 showing, if I wanted to change the dimensions then I have to repeatedly cancel previews until every digit is entered.

Why does Photoshop require such huge temp files plus 10Gb RAM for what is essentially a single action?

Noel Carboni
Braniac
October 10, 2014

The plain and simple fact is that you need a system with a LOT more memory than that to work on giant panorama images.

One copy of that image fits in your entire RAM at one time, and to do any editing at all you need at least two (one to read data from, one to write results to).

So all your system is doing is constantly swapping data to/from disk.  But even having a lot of RAM isn't enough; fast SSD storage is a good idea too...  Even with 48 GB RAM I've had Photoshop write several hundred gigabytes of data to scratch files while working on large panoramas.

-Noel

War Unicorn
Braniac
October 10, 2014

I ask as an enthusiast: Why work on a panorama that big anyway? Is the plan to print out a huge 300 DPI mural..?

What's the size at that DPI? Like 6 feet high, at least? Isn't that overkill?

rcbelmont
New Participant
September 11, 2014

I am having a similar issue. I can barely use the marquee tool the performance is so bad! I even updated all programs this morning, still horrible performance. Please help

New Participant
August 28, 2014

When I added memory, the issue halted. Bite the bullet and invest in your computer. Its worth the cost and your time being frustrated outweighs the impact to your wallet.

New Participant
August 28, 2014

I had this. Massive drop in performance. My solution was mind numbingly easy once  worked out what had happened.

Old version of photoshop had a custom scratch disk setup. ie I had sent the scratch file to a disk of my choosing. The new version defaults to using (in my case drive C on pc) the boot drive or drive photoshop was installed onto.

Could you please compare scratch disk usage across versions and while your at it, memory allocation as well.

Hope this is useful.

Participating Frequently
August 7, 2014

I have the same problem (Win 7 64, 24 gig RAM, 119 gigs HD free). Upgraded from CS5 last Jan and had no problems previously with CS5. Same files from the same DSLR on CC and now it's slow, needs to pause to think for long periods and gets worse the longer I use it. These aren't even big files. I worked with 1.5 gig film scans in CS5 with no problem.

Checked the memory usage and it was using over 19 gigs of RAM despite that the max RAM is set to 13 gigs, same as I had in CS5, all other performance settings are default. Seems like a bug to me.

Would be nice if someone would take this issue seriously and fix it because it's ridiculously tedious to do work in CC and CC doesn't seem worth the money when I had a better-working CS5. I have only one third party filter, DXO Viewpoint 2, which I rarely use. I don't use Bridge or Camera Raw, I just simply edit files using the standard tools.

On a separate note it pisses me off that the shortcut keys are still broken and often pick the last tool instead of the corresponding tool. And now there are a host of new cursor and focus issues.

People considering the upgrade to CC will hopefully see this thread and think twice.

Chris Cox
Braniac
August 7, 2014

What most people will see is that these issues have turned out to be on the user's system, not in the Photoshop program.

It sounds like you have a problem with memory , and with shortcut keys -- neither of which other users are seeing.

That could be due to a buggy third party plugin, or it could be something else on your system.  Corrupt fonts can sometimes cause slowdowns and excess memory usage. But on Windows we haven't seen much that would cause problems with shortcuts.

Participating Frequently
August 7, 2014

I will try removing the one plugin I have and see if it makes a difference.

New Participant
July 14, 2014

Same problem here ... on my old PC PhotoShop CS5.5 worked a lot faster and better.... it's about the user experience Adobe!... now it eats 6GB RAM and I'm just creating images for HTML emailings.. crazy

New Participant
June 27, 2014

Similar problems here on a Mac with 16GB RAM. Downloaded CC this week. Thankfully I didn't delete CS6. Tried to crop a 1.5MB image in CC. After waiting several minutes for the crop operation to finish. I canceled it. Closed CC. In a matter of seconds I opened the file in CS6. Crop completed in a fraction of a second.

Really Adobe, stop with blaming your paying customers! Ridiculous.

Chris Cox
Braniac
June 27, 2014

c-m-c you forgot about the resolution parameter in the crop tool, and created a HUGE file.  Check all the parameters before blaming the software that is just doing exactly what you told it to do.

New Participant
June 27, 2014

Wrong. Resolution was set to 72 ppi in CC and CS6.

New Participant
June 24, 2014

I would like to add my experience to this. I downloaded the trial Photoshop CC and decided not to use it as I was getting similar problems found in this post. I'm not sure you would call it a memory leak.

Yeah Photoshop takes all the memory I have allocated to it (13GB out of 16GB) which I didn't expect. but when I open certain files I have problems. I have one file that was recovered from a crash of CC, every time I open it but it says that it's about 4GB in size (saved as .PSB with 20+ layers) but if I try and open another files which is 35MB or add more layers it says it's run out of memory, but this does not make sense as I would expect to have another 8.5GB to play with ( I have all other application closed)

I have opened another 35MB files and task manager says that I have 3.80GB being used I add 15 duplicate layers and it rises to 3.81GB (Photoshop now says that the document is 552.MB) this seems ok to me

I just don't know why the other file takes the 13GB straight away even though the document is only 4GB. Does this make sense? My only thought is that this photo is corrupted and doing something weird with the

memory.

Kevin

DJ Emir
Participating Frequently
July 17, 2014

I too have a huge problem with the latest version of CC 2014. CS6 was running very smoothly and up until very recent CC was lagging just every now and then but recently took a huge nose dive. First it took forever to save files and now it is lagging more and more just on start up and then on almost every type of function from re-size to moving objects and layers around.

I'm on an i7 2.67Ghz PC running windows 8.1

with 24GBs of Ram and 96% allowed to Photoshop so roughly 22GBs

NVidia Graphics 660 Card with built in 4GB Ram

Level 8 Cache

36 History states

3 Scratch disks: first one a solid state, second a 7600rpm 3TB 6gb/sec Sata drive, 3rd a 3TB 6GB/sec External Drive connected via USB 3.0

5600 Fonts <- could be the culprit (running a font verification script now)

This whole set up was fine and fast on CS6 but after using CC for a little then upgrading, it somehow destroyed both CC and CS6 speeds.

Participating Frequently
July 17, 2014

Not sure if you saw my post but I solved most of my issues by creating a

new window login. I'm not familiar with win 8, but on win 7 64 that did the

trick