- Local time
- 3:45 AM
- Posts
- 8,693
- OS
- Windows 11 Pro + Win11 Canary VM.
Today, I was processing data in a Hyper-V VM with results being written to a physical host drive (using enhanced mode).
I found it was very slow - around a quarter of speed I normally can write to drive.
Did a bit of digging around and found reason (actually remembered is more accurate) was due to the TSCLIENT interface which interfaces the Hyper-V vms to host drives.
I then tried writing to host drive using a network share instead (had to set up permissions for host drive to be shared), and use an external switch.
This was much faster - around 80% of my normal write speed - I expect a little reduction as using a VM.
I then tried an experiment with no idea if it would work. I created a virtual hard drive on the host drive and attached it in Hyper-V settings as a second hard drive. I could see the drive as a normal local drive in the guest. So when I ran the test again (rebooting to clear any cache), it was slightly faster than the network method.
Obviously the TSCLIENT interface is very inefficient!
As an aside, if using W10 Home as a guest VM, you cannot use TSCLIENT anyway, but you can use the network or vhd method - this is easier (in my opinion) than faffing around with making physical disks offline and works even if you only have one drive (you cannot take host OS drive offline, even if partitioned).
I found it was very slow - around a quarter of speed I normally can write to drive.
Did a bit of digging around and found reason (actually remembered is more accurate) was due to the TSCLIENT interface which interfaces the Hyper-V vms to host drives.
I then tried writing to host drive using a network share instead (had to set up permissions for host drive to be shared), and use an external switch.
This was much faster - around 80% of my normal write speed - I expect a little reduction as using a VM.
I then tried an experiment with no idea if it would work. I created a virtual hard drive on the host drive and attached it in Hyper-V settings as a second hard drive. I could see the drive as a normal local drive in the guest. So when I ran the test again (rebooting to clear any cache), it was slightly faster than the network method.
Obviously the TSCLIENT interface is very inefficient!
As an aside, if using W10 Home as a guest VM, you cannot use TSCLIENT anyway, but you can use the network or vhd method - this is easier (in my opinion) than faffing around with making physical disks offline and works even if you only have one drive (you cannot take host OS drive offline, even if partitioned).
My Computer
At a glance
Windows 11 Pro + Win11 Canary VM.I9 13th gen i9-13900H 2.60 GHZ16 GB solderedIntegrated Intel Iris XE
- OS
- Windows 11 Pro + Win11 Canary VM.
- Computer type
- Laptop
- Manufacturer/Model
- ASUS Zenbook 14
- CPU
- I9 13th gen i9-13900H 2.60 GHZ
- Motherboard
- Yep, Laptop has one.
- Memory
- 16 GB soldered
- Graphics Card(s)
- Integrated Intel Iris XE
- Sound Card
- Realtek built in
- Monitor(s) Displays
- laptop OLED screen
- Screen Resolution
- 2880x1800 touchscreen
- Hard Drives
- 1 TB NVME SSD (only weakness is only one slot)
- PSU
- Internal + 65W thunderbolt USB4 charger
- Case
- Yep, got one
- Cooling
- Stella Artois (UK pint cans - 568 ml) - extra cost.
- Keyboard
- Built in UK keybd
- Mouse
- Bluetooth , wireless dongled, wired
- Internet Speed
- 900 mbs (ethernet), wifi 6 typical 350-450 mb/s both up and down
- Browser
- Edge
- Antivirus
- Defender
- Other Info
- TPM 2.0, 2xUSB4 thunderbolt, 1xUsb3 (usb a), 1xUsb-c, hdmi out, 3.5 mm audio out/in combo, ASUS backlit trackpad (inc. switchable number pad)
Macrium Reflect Home V8
Office 365 Family (6 users each 1TB onedrive space)
Hyper-V (a vm runs almost as fast as my older laptop)
