Searching this Forum, I haven't seen a RamDrive mentioned since 2015.
With the Expanded (and Exciting) new capabilities of 1.5, I would think Window's stingy distribution of memory would be an issue. For those with extra memory, the option to move the database over to a RamDrive might be a relatively simple option. I have 16G of RAM and I suspect my 64bit Windows 10 has never used more that 8G. I would think indexes/DB over 1G would be plenty fast when free of Windows Memory Management. With the Ram Drive Installed, all that would be needed is changing pointers to, and placement of the DB. (I suspect)
Example: https://sourceforge.net/projects/imdisk-toolkit/
RamDrive Option
Re: RamDrive Option
As the database is already in RAM why should we need a RAM Drive ?leee wrote: ↑Thu Jun 17, 2021 8:57 pm Searching this Forum, I haven't seen a RamDrive mentioned since 2015.
With the Expanded (and Exciting) new capabilities of 1.5, I would think Window's stingy distribution of memory would be an issue. For those with extra memory, the option to move the database over to a RamDrive might be a relatively simple option. I have 16G of RAM and I suspect my 64bit Windows 10 has never used more that 8G. I would think indexes/DB over 1G would be plenty fast when free of Windows Memory Management. With the Ram Drive Installed, all that would be needed is changing pointers to, and placement of the DB. (I suspect)
Example: https://sourceforge.net/projects/imdisk-toolkit/