![]() ![]() At least a large file is not going to get moved and fragemented by the OS if there's nowhere to move it to. A preallocated disk is not going to get further fragmented, because the files, once created, won't change in size or location on the disk. The best option would appear to be use a preallocated non-spanned VHD and make sure it is not fragmented (or not much). I have iDefrag available to defragment my volumes, though annoyingly (unlike some Windows defraggers) it won't defragment single files it's either the entire volume, or nothing. I purchased a larger disk, so now I have ~100GB free, and I decided to try and figure out the best performance option. Performance had been suffering, and I figured the fragmentation had something to do with it (though I didn't run any tests to confirm this). Two volumes, one 60GB and one 150GB, though the actual file sizes were ~40GB and ~100GB using sparse VHDs. I had been running a VM for a few months and discovered that the VHD files were heavily fragmented - literally tens of thousands of fragments. My own experience applies to Fusion but these issues concern any VM. If someone could direct me to places where I can find out more information about avoiding VHD fragmentation I'd be very grateful. My short question is: how can I create a preallocated virtual disk, of around 100GB, that is NOT fragmented before I even begin using it? Simply having that much contiguous free space is not enough - I made sure of that, and still vdiskmanager created a disk file that is in 139 fragments. ![]()
0 Comments
Leave a Reply. |