keep programs in memory

EnvioX said:

with the consequence that the RAM cannot be managed properly by windows.

The only reason why I use Primo Ramdisk is exactly BECAUSE Windows is quite simply incapable to manage my RAM properly in ALL situations the entire time. The Dynamic Memory Management (DMM) option of Primo Ramdisk lets me effectively work around that problem, at least for how I (personally) use my laptop.

Often typically, significant real-world benefits can only be achieved by applying some advanced/semi-advanced knowledge about the old subject of performance optimization. Moving data back and forth between an SSD and a ramdisk can be incredibly fast especially if you have a fast NVMe SSD, but it's not instantaneous, and, it still eats SSD bandwidth and memory bandwidth until the copying is finished. In fact it also eats memory bandwidth each time when a running process reads/writes data from/to the ramdisk, and eats memory bandwidth regardless of whether this process is accessing the SSD at the same time when it happens. Bandwidth affects the throughput of data transfer operations, you only have so many PCIe lanes in the hardware for passing the data through. So, even though it should be completely obvious that the goal is to avoid accessing the SSD because RAM is faster (and no, RAM being a whole lot faster than an SSD is not just a perception─LMAO!), there are still a few technical limitations to also want to keep in mind. After all, choosing to store data on a ramdisk still eats RAM space, with or without DMM so, you might bump into situations where things will run slower as a result of having not enough available RAM space to work with, especially if you already don't have that much physical RAM installed to begin with. Either way, it can still be possible to avoid that, e.g. simply by freeing up (manually or programatically via scripting/automation, etc.) some space on the ramdisk immediately when feasible. This is because the DMM feature of Primo Ramdisk lets free space on the ramdisk be used by Windows and by apps running.

TairikuOkami said:

You can try Processs Lasso and prioritize those processes.

It doesn't give you direct control over the memory use of the processes, even though it does give you memory control features with things like being able to adjust memory priority and SmartTrim.

Ram disk would help, if you would move their temporary/working folder there, not the program itself.

This is a common misconception. The SysMain service does not give you direct control over which programs are retained in memory, as instead it learns ("black box" style of behavior) to merely pick the ones that you open the most frequently. You need to open/close the program in question a few times in a row before SysMain arrives at the conclusion you want to teach it. So, in situations where the goal is specifically to be able to more quickly open/reopen a program that is too infrequently used for SysMain to decide to retain it in memory─or that is currently no longer being retained in memory by SysMain due to too much memory having been used by other programs that requested the memory─you really don't have that many alternative choices besides putting the actual program itself on a ramdisk, and to keep it on there for some period of time. That is, for as long as the pros still outweigh the cons (if possible). But yes, Process Lasso Pro can also be used to continuously monitor these performance related factors, and to trigger an action when certain criteria are met. An example of such an action could be to run a batch script which, among various other things, performs the task of freeing up some space on the ramdisk, e.g. by deleting the copy of the program that was stored on the ramdisk. Thus allowing Windows and other programs to reclaim the resulting memory space after it is released by the DMM feature [of Romex Software Primo Ramdisk]. By comparison, ImDisk is more primitive and less flexible, but results can still be similar, at least depending on what it is that you are trying to achieve.