Skip to main content
Known Participant
October 5, 2023
Question

25 years later why is PS still hogging memory?

  • October 5, 2023
  • 3 replies
  • 467 views

I can't understand why PS hogs so much memory - it has done this since I first started using it 25 years ago. Example: when I first launch PS it is using 1.6 GB of memory, a day later without any files open it is using 10GB - what on earth is going on?

This topic has been closed for replies.

3 replies

Known Participant
December 16, 2023

Well it has got to the stage now where I am looking to bin Photoshop after 25 years of paying for it.

It's an absolute joke that it works perfectly well when it first launches and uses less than 2GB of memory and then an hour after it is working exactly the same but hogging 13GB of memory and causing my other applications to run slow. 

D Fosse
Community Expert
Community Expert
December 16, 2023

@JasonBatley 

 

There are only two things that will make Photoshop slow your whole system down.

 

One is that you have insufficient scratch disk space. You'll realistically need at least 100 GB for any normal work, but in some cases you may need 500 GB or more.

 

The other is that you set memory allocation too high in PS Preferences. Don't go above 70% or so, other processes need memory too. Even ACR needs its own memory outside Photoshop.

 

Few people have any idea how much memory is required by advanced raster image editing. It's not Photoshop, it's the sheer amount of data. RAM is just a tiny part of it - the total memory needed is normally far more than any RAM installed. Every history state for every open document has to go somewhere.

 

That's why you set a limit in preferences, and that's why Photoshop uses the scratch disk.

 

Normal behavior for Photoshop is to saturate the available RAM very quickly. The rest is handled by the scratch disk. This is dynamically shifted back and forth, so that RAM acts as a cache for the scratch disk's main memory.

 

In short, 13 GB is nothing.

Conrad_C
Community Expert
Community Expert
October 6, 2023

I see this on my Mac too, it allocates 1.75 GB on startup. I think what it does at startup is pre-allocate memory, and that is probably for performance reasons.

 

This is not an official Adobe explanation  because I don’t work there, but this might be what is going on: One of the things everybody wants to avoid is an application being slow and laggy, and one way to avoid that is to load as many application components as possible into memory in advance. Photoshop probably loads the most commonly used features, fonts, filters, etc. before you start editing, so that when you ask for them, there is as little loading lag as possible.

 

I also started two other photo applications that have a similar feature set, and they do allocate a lot less memory at startup. So maybe Photoshop could pre-allocate less. Why doesn’t it? One reason might be that it is the oldest, so maybe there are aspects of the 30-year-old software architecture that keep it from loading less until more of the application can be rewritten. But it is also possible that it isn’t necessary to allocate less. There is a popular saying in the software engineering community: “Unused RAM is wasted RAM.” That’s because RAM is both expensive and fast, so it should be maximally used whenever possible, otherwise you paid a lot for GB that are doing nothing. Now, of course running low of RAM is bad when it means other applications are being starved, but as long all running applications are getting what they need, there is no problem using more RAM as long as there is a benefit. (So this doesn’t excuse inefficiency.)

 

The other observation is that although other photo editors allocate less memory at startup, they aren’t the applications most people choose. Photoshop is. So maybe there is a benefit to the additional RAM allocation that helps make Photoshop the application that people want to use.

Known Participant
February 6, 2024

This doesn't make sense to me as it works perfectly well using 2GB of memory but it gradually grabs more and more until my system grinds to a halt - why can't it just carry on using the 2GB? I'm only working on one small file at a time.

D Fosse
Community Expert
Community Expert
October 5, 2023

This is something you just have to get used to. Raster image editing moves huge amounts of data around, and it all has to go somewhere. It's not Photoshop, it's the sheer mass of data.

 

 

 

Known Participant
October 6, 2023

As per my original post, this is happening with no files open.

D Fosse
Community Expert
Community Expert
October 6, 2023

If you've had files open, that memory is not released until you exit the application. The memory is recycled and reused.

 

This is by design, to avoid requesting memory from the operating system over and over again. That may not matter so much for a single file, but it would cripple batching and high volume processing.