But for example Photoshop lets the user specify the amount of RAM that is to be used by it. That [I guess] would be a solution to this issue in Mp3tag
I can. But how will it help?
I did not know if this RAM purge / retaking of RAM from Mp3tag was triggered by some process / third party software or just happens gradually over the time, because I have not observed a pattern yet. My report of behavior was just a statement of fact with the minimal output of data: a difference in time it takes to perform a re-load shortly after initial load-up of files and a re-load performed long time after such initial load-up. So when should I take that screenshot: before load-up and / or immediately after it and / or some time after and / or long time after it; prior to a re-load which turned out to be a slow one? We want to see how much RAM is used in a given moment?
If yes, then I did now some tests with the help of Resource Monitor. I was never able [like during a load-up of more and more files to CorelDRAW] to get my
Standby RAM lower than ~125 MB. And after stopping the filling-up-process it steadied at ~400 MB of
Standby. And the overall observations are consistent with my predictions: the more RAM is grabbed by other programs, the more likely Mp3tag will loose it hold on it- thus making the re-load of files slower. And when RAM is fully utilized then even an immediate re-load will be slower. And sometimes after closing other software and gaining as little as 500 MB of
Standby RAM the re-upload process to Mp3tag becomes faster - while at other times I needed more than that despite still using the same set of files. [Trying now to figure out what program affects how this process would be a tedious work and not really beneficial to the case]
But in the light shed by my tests: cannot Mp3tag be told to hold on to once acquired parts of RAM? Cannot the user be allowed to tell Mp3tag to hold on to the grabbed RAM- and by grabbed I mean at least that part of it that was needed for the load-up of the current set of files? All of this could be definable in Options [with the current state of things / inner workings being the default ones]
Or would this be precisely what you had in mind when you wrote about the outcome?
As for a workaround
Should I just insert physically more RAM to the system?
I have 16 GB; of which during a normal usage 3 GB are left on
Standby and 6.5 GB are shown in Resource Monitor as
Free. But as my long time experience and nowadays test show, that unused half will be taken by big pieces of software like Photoshop and Corel and used up with time as the work in the progresses