Hi Matthew,

It would be great if you can elaborate on your question for greater clarity. I feel that flat file repository may be a single point of failure and there may be a bottleneck in performance in the long-run.

Thanks.

I agree with Jeff.

We, VMware, absolutely recommend using PVSCSI for DB workloads. PVSCSI enhances performances and also facilitates more queues to the vmdk's , hence more channels to the luns.

I am more worried about using pv SCSI for non DB workloads.

Any reason not to use it?

Sent from my iPhone, please excuse typo's

Nope, PVSCSI is available if you need that extra boost, it does not hurt to use it., For example, I have customers who are using PVSCSI for RHEL OS vmdk's in their production env, RHEL out of the box provides pvscsi support, OS disks are not IO heavy but they like doing this just to ensure that they have reserve boost in case they need to use that SCSI controller for some other vmdk's which may take advantage of pvscsi capabilities....

Customer is looking for a Recommendation on using PVSCSI vs LSI Logic going forward for all VMs.

Thoughts?

Sent from my iPhone, please excuse typo's

-For high IO workloads , DB/Non DB, PVSCSI controllers are recommended for hosting that application VMDK's.

-you can use LSI logic as the SCSI controller for that OS vmdk if you do not see a lot of IO's on the OS disk.

-HTH

Like I said, might help, can't hurt. I would always load pvscsi, personally.

never hurts as Jeff said, keep in mind for the OS Vmdk to be supported by PVSCSI controllers, the OS has to natively supoort it, RHEL does that for a fact ,  OEL UEK does not .

Good point. Customer is using RHEL.

Sent from my iPhone, please excuse typo's