我们正在考虑构建单独的VMware Horizon视图群集，并使Nutanix-Cluster仅用于服务器负载。
我们有一些创建这个的情况。其中一种是购买4个新的VMware主机，并使用ISCSI将它们连接到现有的Nutanix群集，这仅仅是因为我们已经在现有群集中有足够的存储空间。
我的问题是，使用ISCSI是瓶颈吗？我们将运营大约260个Win7/Win10任务工人VDI客户。
问候
托比亚斯
最好的答案乔恩
\n\nI dont work in Sales, but if you'd like to play around with some configuration ideas, drop me an email at jon at nutanix dot com and I'd be happy to put our heads together on the technical bits.
\n
\nRE VAAI
\nWhat I'm talking about is VAAI for block storage, which all VM's use in one fashion or another when you run a VM on a VMFS volume. Specifically a VAAI primative called ATS, we do not support (yet) on ABS. That has to do with array assisted LUN locking in VMFS. Before ATS was introduced, LUN locking was a huge problem in VDI and server virtualization.
\n
\nAlso, if you run VM's on an ABS volume, we lose all ability to control those VM's at a per VM level, so you will see the VM's \"drop out of\" prism reporting.
\n
\nLastly, a single ABS volume uses one oplog volume, whereas each VM virtual disk uses one oplog volume. This has to do with how write caches work within Nutanix. This means that you're going to go from a good amount of write cache per VM, to drastically less write cache shared across many VM's on an ABS volume.
\n
\nNet Net, while ABS technically could do the job, it's really meant for different use cases on bare metal servers, or scale out storage on high end database workloads (VM or physical)","className":"post__content__best_answer"}">
