Multiple PVSCSI with SQL Server

[JoseTeixeira]

Hi,

Regarding SQL Server virtualization, been trying to find info if there is a positive performance impact on separating Data devices from Log devices into different Paravirtual SCSI Adapters, similar to what is done here [https://books.google.pt/books?id=jrMTBAAAQBAJ&pg=PA155&lpg=PA155&dq=pvscsi&f=false].

There has been a scenario on a client where an additional PVSCSI was added and log devices were separated to the new PVSCSI, showing considerable performance gains. Yet, the doubt remains if it was due to this separation or simply due to the fact that an additional PVSCSI was now present.

Anyone has any insight on this?

Thanks in advance

[MKguy]

Each controller has it's own IO queue with a certain maximum queue depth. By adding additional controllers, you can prevent the queue from overflowing in cases of really high IO workloads (if you physical storage is not the bottleneck already), so it's generally recommended to split different heavy IO virtual disks to different vSCSI controllers as well.

You may also want to consider increasing the controller queue depth:

VMware KB: Large-scale workloads with intensive I/O patterns might require queue depths significantly greater than P…

[JoseTeixeira]

Thanks for your attention and reply MKguy‌

I should've expanded the question a little further:

Log disks typically are written in a sequential manner, while data disks follow a more random pattern on their r/w, and it is well known that data and log files should be on separate disks due to this difference.

But what about the controllers? Is there a benefit also on keeping these different patterns in separate PVSCSI controllers?

[BoneTrader]

check out ->  http://www.pearsonitcertification.com/store/virtualizing-sql-server-with-vmware-doing-it-right-9780321927750

[JoseTeixeira]

An answer to the question was posted here:

virtualisation - Multiple PVSCSI with SQL Server - Database Administrators Stack Exchange