We did some benchmarks back in 2019 with Arsenal image mounter (as I don't think there is another other solution that supports the same range of disk image formats). I think all the available options are in the help file. LIMITATIONS: The disk must be mounted using physical emulation option. This means the orginal disk image is never modified and all changes get added to a separate delta file. With this option the virtual disk is backed by the '-f' image file and an existing write cache file (.osfdelta). There is also a 3rd option which is "-t file+wc". It will generally be a lot slower than a RAM drive. But some caching in RAM can still happen. img file (the new volume is backed by a file and not by virtual memory). Using the -t file option means all reads and writes go back into the. Manually saving a RAM drive back to disk will be slow, as typically disks are pretty slow. So changes to the RAM drive are lost (unless you manually save it). Once this happens there is no mirroring or backups back into the on disk. Adding the -f option, pre-loads a disk image into the RAM drive. If you don't have enough free physical RAM, performance will drop off a cliff as the operating system will start swapping to disk. If you have enough free physical RAM, this will be a very fast drive. So the content of the drive is stored in virtual memory. Using the virtual memory "-t vm" option on the command line creates a RAM drive.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |