finagle Posted August 24, 2020 Share Posted August 24, 2020 When opening a file, if the application estimates that the file will require swap memory, it should allow an optional configuration which when enabled will provide an advisory to the user with an estimate of impact on memory usage. I've been working with panoramas lately, and some of these files get very large. Although my machine has a lot of RAM and available NVMe SSD for swap, it is not always obvious when a file is too large to realistically work on. It would be useful to see an estimate before continuing with file opening rather than the machine blocking for hours and then failing to open when it hits the disk safety limit. I appreciate there is internal compression going on to optimise memory usage, but I'm sure you can make a finger in the air estimate based on the current machine (RAM allowed and swap space available), image dimensions of the file, bit depth and a fudge factor to give a warning roughly on the lines of 'this might need swap space', 'this is definitely going to be slower to process', 'you might want to close some other images first', 'heck no I'm not opening this' . This might help reduce the number of times I have to resort to Force Quit to do memory management when a well compressed file turns out to explode in size in AP. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
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.