I discovered IMDisk and it is really great piece of software. I especially appreciate the possibility to create ramdrive as needed by the command line.
I know this was discussed before here, but I need to clarify the question of memory allocation for Ramdisks.
I understand that there are two options - standard using virtual memory (which is simply general memory allocation managed by Windows) and special using awealloc driver that allocates physical memory.
I have 64 bit Windows 10 and 16 GB RAM. I will use RAMdrive for working files, not for swapfile or other system files. Typical size of the drive will be 2-3 GB RAM.
I generally like the idea of allocating memory from the virtual Windows pool, because Windows memory management is generally working well (better that many "optimizers"). I need smoothly running system, since some apps that will be working with files on ramdisk need good performance overal and also I like to have fast, responsive system. But I have read in some discussions here before that it can under some circumstances make problems with Windows memory allocations, because "a large chunk of memory is allocated". But those threads were mainly about older computers, 32 bit, WinXP/7.
So I would like to ask
1. Are the described limits with IMDisk virtual memory Ramdrives specific for older computers, with 32 bit Windows (which has limited address space)?
2. Can I use in my configuration ramdisk with described parameters without performance degradation/memory allocation errors?
3. Will IMDisk well handle 2-3 GB ramdrive created in virtual memory on Win64 without measurable/perceivable performance degradation of the whole system?
Thank you in advance
Edited by jumpingjackflash5, 2 weeks ago.