Hi, little question about a Dynamic RamDisk and usage of NTFS Compression. This doesn't seem to work ? I understood the latest versions added support for NTFS Compression ? Please see attach. This RamDIsk contains 9,5 GB of data, everything is NTFS Compressed. Memory usage however is saying it uses about 19,7 GB, so almost the size of original contents without compression. So even though windows explorer seems to be fooled about it completely, simply looking at mem. use shows that the compression is either not used/done or it doesn't actually compress the space used somehow ? Could you shed a little light on this please ?
I came across this too :D v77 is basically right ^^ But in addition some details:
You need to keep the sectors in RAM (analogous to sectors on HDDs) if they are partly used.
This is as more size consuming for RAM as bigger the automation allocation settings of the RAMdisk is set. You can defragment the ram disk to move the data together and fill the gaps
This is because of the NTFS compression handling creating lots of fragments. The files are first written uncompressen and then perforated with free space in sectors where compression is possible. This happens on any NTFS files with compression. The space in mid of sectors will not be released until the old file structure goes through some NTFS magic - can be forced by defrag. ;)
Unsuitable for many write accesses, but practically to minimize holded quickly accessible data.
Last edit: Eld0r 2018-10-30
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi, little question about a Dynamic RamDisk and usage of NTFS Compression. This doesn't seem to work ? I understood the latest versions added support for NTFS Compression ? Please see attach. This RamDIsk contains 9,5 GB of data, everything is NTFS Compressed. Memory usage however is saying it uses about 19,7 GB, so almost the size of original contents without compression. So even though windows explorer seems to be fooled about it completely, simply looking at mem. use shows that the compression is either not used/done or it doesn't actually compress the space used somehow ? Could you shed a little light on this please ?
For various reasons, RamDyn is not designed to work with compressed file systems.
There is no risk of data loss, but memory is not properly released.
As I want to give the user as much liberty as possible, I prefer not to prevent him to try that, but perhaps I should add an information in a tooltip.
Understood. Was worth a shot though :-) Thanx
I came across this too :D
v77 is basically right ^^ But in addition some details:
You need to keep the sectors in RAM (analogous to sectors on HDDs) if they are partly used.
This is as more size consuming for RAM as bigger the automation allocation settings of the RAMdisk is set.
You can defragment the ram disk to move the data together and fill the gaps
This is because of the NTFS compression handling creating lots of fragments. The files are first written uncompressen and then perforated with free space in sectors where compression is possible. This happens on any NTFS files with compression. The space in mid of sectors will not be released until the old file structure goes through some NTFS magic - can be forced by defrag. ;)
Unsuitable for many write accesses, but practically to minimize holded quickly accessible data.
Last edit: Eld0r 2018-10-30
Nice, but how to defrag a Dynamic Ramdisk mounted as a Mountpoint (not as a drive) ?