XPost: alt.os.linux.mint, alkt.os.linux.mageia   
   From: nospam@needed.invalid   
      
   On 10/27/2023 11:21 AM, Mark Lloyd wrote:   
   > On 10/26/23 16:40, Big Al wrote:   
   >   
   > [snip]   
   >   
   >> Not much demand here.  I didn't hear "games" so you've got a simple task.   
   >   
   > Virtual Machines can take a lot of RAM. Also, they're slow if you don't have   
   a NVMe for storage.   
   >   
   > [snip]   
   >   
      
   You can put the whole thing in RAM.   
      
   I routinely put entire containers in RAM, temporarily, and   
   if the session is a "keeper", copy the container back to storage.   
      
   It typically has I/O limits, even with paravirtualization.   
   Only very recently did the I/O rate change.   
      
   On Linux, you can use TMPFS for the ramdisk. On Windows, there   
   is a separate utility, third party (OSFMount) which is handy   
   as ram storage for filesystems.   
      
   But before anyone gets carried away, the RAM does not add that much   
   to the experience, except reducing wear on your SSD if it is running   
   for a while. It was more of an "option" when the main storage was   
   hard drives, and the hard drives were slow.   
      
   A desktop limit today is 128GB, 4x32GB sticks, for about $400.   
   On AMD, the hardware could likely take more, say using 64GB sticks,   
   but they don't allow that. Because to them, we would be   
   "building cheap servers, biting into Epyc market".   
      
      Paul   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)