When copying files from the guest to the host with VMware Tools (not using SMB, FTP, etc …) the mechanism is very inefficient.
Consider the following scenario assuming a 10GB file to be copied from the guest to the host:
- VMware Workstation copies the file from the guest to a temporary location on the host system.
- Windows Explorer *copies* the file from the temporary location to the desired location on the host.
Assuming the destination location is on the same volume as the temporary location twice as much storage space as should be needed is used. In addition, the temporary file is not removed, so the wasted storage space is retained indefinitely until a background process performs clean-up of temporary files. For large files, this process means the copy takes around twice as long as should be required given the redundant second step.
I’d suggest the following changes:
- Where the destination location resides on the same volume as the temporary storage location a move should be performed resulting in no wasted space and a halving of time required.
- If the destination location resides on a different volume from the temporary storage location, the data should be removed from the temporary location after the copy is completed.
- Ideally the file should be directly copied to the destination location instead of using an intermediate temporary location but I expect there are additional factors here. The above suggested improvements should apply to the vast majority of copy operations while being relatively simple to implement?
All testing performed on Windows 10 v1903 x64 w/ VMware Workstation v15.5.0.
Thanks in advance.
To see the full content, share this page by clicking one of the buttons below