大网数据广告活动
服务器运维问答

How can I determine the performance penalty of VT-d vs. baremetal?

· 52CE 我爱测

I am looking to configure my server in a slight odd way to create a private cloud setup. I have to take the HBA that my storage disks are tied to and pass it into a VM (probably xen) to allow the creation of a vSAN type setup. I …

问题原文

原帖链接 · AtomicPorkchop · CC BY-SA 3.0

I am looking to configure my server in a slight odd way to create a private cloud setup.

I have to take the HBA that my storage disks are tied to and pass it into a VM (probably xen) to allow the creation of a vSAN type setup. I want to do this so I can implement a SAN type setup within a single server.

When I was asking around people were telling me the IOPS would not be as good as baremetal. I kinda of factored that into my setup, but it got me wondering just how much would it be hurting the system?

Also someone mentioned that the VM running on the baremetal but having a storage controller passed in creates an odd dependency loop since the VM still relies on the host for the memory. Other than it being a pain to troubleshoot does it really cause any significant degradation in performance?

Oh yeah by the way the filesystem mainly in question here would be ZFS. Probably running on FreeBSD (including things like FreeNAS and NexantaStor) or OpenIndiana.

Thanks!

已采纳解答

原帖链接 · ewwhite · CC BY-SA 3.0

A real answer, though.

Yes, there's a potential for latency or a performance hit from running your storage in a VT-d passthrough.

But think about the practical aspects. Your system isn't going to be IOPS-bound in the first place. There are several levels of abstraction in this storage, and the fact that you're using VMs at all indicates that you're okay with the tradeoffs compared to bare metal.

The real concern you should have is whether the solution will work at all! VT-d can be temperamental and doesn't work with every adapter.

So test for yourself with your workloads!

摘自公开归档,保留原文语言,版式经整理,外部媒体与邮箱地址已移除。

资料来源与适用范围

资料来源
Server Fault
适用范围
以原帖系统、软件版本与发布日期为准(2016-02-04)
内容语言
中文;命令、路径和错误标识保留技术原文
本地收录日期
2026-11-15
授权说明
CC BY-SA 3.0

正文与所需资源由本站本地存储。查看来源及更新记录 ↗

请按适用版本和实际日志确认原因;本站没有对每一种系统或设备逐项执行文中的操作。