Abstract
Many traditional physical storage workloads are well understood. Quantifying how access patterns change when a hypervisor in inserted in between server applications and physical storage requires rethinking what is optimal for a NAS configuration. This presentation will examine several Hyper-V workloads from the perspective of an SMB3 implementer.
Learning Objectives
What is required set of SMB3.0 features to support a Hyper-V workload? How should I prioritize my SMB3 feature development schedule for Hyper-V?
How does the Hyper-V map guest I/O requests into SMB2/3 operations? What is the new distribution and size of requests?
What is the performance impact of SMB2/3 feature such as LargeMTU, SMBDirect, and the “File Level Trim” IoFsControl?