Hyper-V virtual controller for I/O intensive drives?

Good morning,

In the world of VMWare where I’m far more comfortable, it’s always been best practice to run I/O intensive applications (Read: SQL, SQL, SQL, and maybe large file servers w/Windows Dedupe enabled) with a dedicated virtual storage controller (namely a pvscsi)
for the VVOL/VMDKs

I can’t find any documentation anywhere, from anyone on what the Hyper-V synthetic/virtual SCSI Controller limits and/or best practices are for such workloads, let alone where the tipping point is to adding another one.

Thoughts or links to material I could go through?  I feel like I’ve exhausted Google and Microsoft’s material.

Read full post . . . .

Go Que Newsroom Categories

Fatal error: Allowed memory size of 67108864 bytes exhausted (tried to allocate 53 bytes) in /home/content/36/8658336/html/goquecom/wp-includes/wp-db.php on line 1995