Thanks Bill, and a great point. We've found that technologies like PVS allow for RAM to be used to offload READ operations, which then provides the ability for SSDs/EFDs on the backend to be dedicated for WRITE workloads. Traditionally hardware vendors have pushed SSD/EFD technology to solve things like "boot storms", which are very read intensive and short, infrequent operations. But once the workload moves more towards "steady state", it does indeed become a much more WRITE-heavy profile. 

PVS won't have a change on the WRITE IOPS per se, but choosing where you store the write-cache is definitely an important consideration when designing/building a PVS-based solution. I've personally found a lot of customer networks cannot provide the consistent performance required to store the WC on the server, and don't personally like using RAM on the client. With VMs, using a small thin provisioned disk has worked quite well, and as mentioned, can be stored on EFDs since the PVS server is offloading the READ operations in RAM. 

What would you like to see in an article/post focused on the impact of PVS to write cache? Where to locate it based on the IOPS required? Sizing for write IOPS maybe?

Thanks Bill!