Jump to content
You must now use your email address to sign in [click for more info] ×

Recommended Posts

  • Staff

Hi Malcolm Tinn,

Welcome to the forums :)

There is no feature like this I'm afraid however it has been requested in the past so it might be considered in the future.



Please tag me using @ in your reply so I can be sure to respond ASAP.

Link to comment
Share on other sites

14 hours ago, Malcolm Tinn said:

Scratch Disk may be the answer for me and others in this situation.

Does PS' performance slow down to the Affinity level when you disable the scratch disk option?  

AP, AD & APub user, running Win10

Link to comment
Share on other sites

44 minutes ago, IanSG said:

Does PS' performance slow down to the Affinity level when you disable the scratch disk option?  

Longer answer:

PS needs a fast scratch disk to maintain its performance because it can create huge numbers of 'scratch' items that have to be stored somewhere for as long as they are needed. For large documents with lots of layers these files require much more storage space than even a system crammed full with as much RAM as it can support, so they are offloaded either to VM (virtual memory) disk space under the control of the OS, or to one or more scratch disks designated in & controlled by PS itself.

If the scratch disk(s) & the interface(s) to them are faster than what the system can provide via its built-in VM management, then the performance boost is considerable. This also has the advantage, particularly important on systems with relatively small SSD's, of providing lots & lots of scratch space that does not have to be shared with system or other applications.

However, offloading anything to VM or even to very fast scratch drives is still much slower than if everything could be stored in RAM, so the Affinity approach is to minimize the amount of RAM required to edit documents to avoid that whole issue (& the expense of extra dedicated drives). But how well that works in the real world depends on several complex interrelated factors, including how much RAM other processes running at the same time on the computer need, how the OS prioritizes memory swaps with VM for all active & inactive processes, if & where a saved version of the document might be stored, & some other arcane stuff mostly related to the particulars of the OS, its memory management system, & how well (if at all) hardware GPU acceleration is implemented in the app itself.

So while there is no simple answer for this, currently the Affinity approach works much better on Macs than on Windows PCs. I know they are working on improving Windows version performance, & while scratch disks may be the way to go for them, it probably won't be as important for the Mac ones.

All 3 1.10.8, & all 3 V2.4.2 Mac apps; 2020 iMac 27"; 3.8GHz i7, Radeon Pro 5700, 32GB RAM; macOS 10.15.7
Affinity Photo 
1.10.8; Affinity Designer 1.108; & all 3 V2 apps for iPad; 6th Generation iPad 32 GB; Apple Pencil; iPadOS 15.7

Link to comment
Share on other sites

I remember the many happy hours I spent learning VM management strategies for the VAX - and how little real effect it had!  Maybe I'll invest some time in learning about Windows' specifics.    

AP, AD & APub user, running Win10

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

  • Create New...

Important Information

Terms of Use | Privacy Policy | Guidelines | We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.