![]() We'll look to see if we can optimize loading of the image back ram disk. ![]() The question is now do you really need the image in Memory, or more concern that you can read/write the image? If you don't care for the image to be in memory, you can use "-t file" option instead and OSFMount will mount the image and you should have "immediate" access to the new drive. You can also verify this by opening Task Manager and locating the correct "System" process (sort by memory used) and looking at the Disk use for the same process while you run your ". If you know what type of drive/model you have you can look up the read speeds for it. HDD with 160 MB/s Read Access, 16 GB / 1610 MB/s = ~100 seconds. SATA SSD with 600 MB/s Read Access,16 GB / 600 MB/s = ~26 seconds. M2 NVMe SSD with 2500 MB/s Read Access, 16 GB / 2500 MB/s = ~6.4 seconds. The delay time you are experiencing can be calculated by taking (Total Size of Image) / (Bytes Read / Sec of drive with the image). the read and write operations are all queued up by the OS/system and control is returned to OSFMount while the operations are still in process). (To a lesser extent, there is some cache affects, i.e. For the most part the bottleneck is the read speed for the drive the image is located on since the image needs to be loaded into RAM before being used. ![]() Upon further investigation, I'm pretty confident the issue is with what we thought it is. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |