I don't entirely disagree with you @D Fosse , but there are instances when Photoshop gobbles up memory like there is no tomorrow and other image editors use far less memory compared. For example, I have three images: a 16bit greyscale image an 8bit RGB image an 8 bit normal map image All are 32.000 by 16.000 pixels Photoshop The 8bit image is loaded first. The 16bit grey image is placed as a smart object. So is the normal map. Memory usage Private Bytes 24,811,532K | Working Set 16,818,216K PhotoLine All images are loaded as-is, with the 8bit RGB file loaded first. PhotoLine doesn't require smart objects to maintain each layer's bit depth, resolution, colour space, image mode, etc. All data are maintained by default on a per-layer basis. Memory usage Private Bytes 9,144,004K | Working Set 8,522,088K With the same layer stack, images, effects, and adjustment layer mask, PhotoLine draws on average 50% less memory than Photoshop. The developers of PhotoLine are known to optimize their app in this regard. Affinity takes up as much memory as Photoshop with this task. More, actually. In short, both Photoshop and Affinity could be optimized further in how they utilize memory. As far as batch processing is concerned: Photoshop is slow --dead slow-- compared to other options (including PhotoLine). It can take ages for a batch to complete when other apps finish in a 10th of the time, mainly because Photoshop wants to open each image in the view. This could be radically optimized in my opinion. What is also frustrating at times is that Photoshop refuses to release memory when files are closed. You @D Fosse already mentioned this. Affinity shares this (at times) inconvenient behaviour with Photoshop. PhotoLine just releases its memory nicely. Well, at least it is possible to force Photoshop to release memory by holding down ALT and then choose the Help-->About option... 😉 Lastly, Photoshop does take up an inordinate amount of memory just for the base application in my opinion. I suppose the legacy libraries and developer addons throughout the years have turned it into memory pacman 😄 The balance between functionality vs memory usage seems inbalanced towards the latter. Even Blender 5, which features FAR more functionality as a whole than Photoshop, takes up 800MB working set memory (that's with many addons loaded!). PhotoLine's executable asks for a mere 437MB. Compare with Photoshop's 3,6GB and I start wondering why so much memory is required for the base application, because its feature set is good, but it's still an image editor. Affinity takes up as much memory for its core app, but that can be explained away since it combines three apps in one. Sure, PhotoLine misses the AI functions (I hear you crying out loud); yet Krita, which offers a similar feature set, and has a good AI plugin, combined asks for around 510GB of memory... I know, I know: comparing apples and pears and oranges. Still, Photoshop strikes me as an app that could benefit from a code cleanup. Possibly a rewrite from scratch. We all know that its core contains legacy outdated functionality (16bit mode, destructive masking/channel operations, limited layer masks, limited image dimensions, etc) which haven't kept up with the times. All that said, context remains important. Loading those three images in Blender's compositor leads to it devouring 39GB of memory... Photoshop looks alright compared 😄
... View more