如果您将Windows 10作为VM OS提供，那么您需要不超过1GB的FrameBuffer
由于您的用户数和密度与您的vGPU配置文件直接相关，因此您需要准确计算您计划移动到系统的用户数。
否则，您将要么低估一切，这意味着您将需要购买更多的单个服务器，因为它们不是一个足够的规范，或者您将过度规范它们，并浪费资源。
你需要对你的数字更准确，而不仅仅是说“大约50到100”。
另外，您的其他基础设施呢？
您是否考虑过额外的存储I / O和网络带宽？
...当添加50-100个使用视频的用户时，您需要考虑所有资源。
这不是一个理论，它是一个事实:-)不要看单个组件价格，看看整个系统的成本。
可以共享相同资源的用户越多，整个系统的成本效率就越高，这也是我们虚拟化的主要原因之一（以及NVIDIA GRID甚至存在的整体原因！）;
最终，为了获得更好的资源利用率，因为它总体上比为用户提供他们自己的专用硬件更便宜。
它不仅仅与物理服务器有关;
机架空间，电源，冷却，许可，支持，维护，升级，更新等等都需要花钱。
服务器密度越高，系统实施和支持的成本效率就越高。
你没有要求M10和M60之间的性能比较，你问M60是否值得K2的购买价格的两倍，答案是，（更详细一点）它比单位购买更多
价钱。
M60显然比M10更强大，但是M10的密度表现更好。
基于FrameBuffer，M60将比M10支持少50％的用户。
您可以在此处了解计划添加到系统的用户数量，以便进行适当的规范和设计。
假设您总共有64个用户（在“约50 - 100”范围内）：
如果每个服务器最多有32个用户，我会说为每个服务器购买2个M60，并为每个服务器提供1GB的vGPU配置文件。
原因在于，M60拥有比M10更多的H.264流（36对28），并且当您计划提供视频时，这是一个重要的考虑因素。
如果您想在系统上添加更多用户，您现在需要考虑我上面提到的有关成本与价值的因素。
您现在需要购买额外的服务器资源以支持额外的用户密度。
此外，如果服务器上的用户较少，则需要较少的CPU和RAM来支持它们;
这是可用于抵消额外服务器资源以支持更多用户的资金。
假设您有超过65个用户（超过M60s FrameBuffer容量和2台服务器）：
对于具有1GB vGPU配置文件的每台服务器超过32个用户，您将需要使用M10。
M10将完成这项工作，但如果同一服务器上的所有用户同时开始观看视频，您可能会开始降低性能。
请记住，一旦用户连接，您就无法在主机之间对VM进行负载平衡（但是您可以在今年/明年之后进行...）。
此外，您的服务器密度将取决于您尚未提及的CPU和RAM规格。
尽管如此，如果您只有2个新服务器并且想要支持超过64个用户，那么每个服务器中的一对M10是您唯一的选择，因为M60只是没有FrameBuffer容量来支持超过64个
用户。
您需要具有H.264解码功能的瘦客户端。
通常，具有SOC（片上系统）或专用GPU的东西将具有该功能。
“Raspberry Pi”将是最便宜的选择，然后你会有很多不同的选择。
英特尔NUC制造出极佳的瘦客户机，有很多不同的型号可供选择，如果你不需要最新和最强大的，它们也很便宜。
瘦客户端仍然是系统中非常重要的一部分。
由于用户体验不佳，瘦客户机选择可能会破坏设计完美的后端系统，因此请确保您测试各种供应商品牌/型号并正确验证它们。
并且不要低估将视频流式传输到可接受级别所需的内容。
正如我最近在这里发布的其他人所提到的，我个人认为流媒体视频是最难做的事情之一，因为它需要随时提供近乎完美的视觉效果和音频。
观看视频的人立即可以看到视觉质量或帧速率的任何下降，其中使用Outlook或键入文档的人可能不会注意到视觉或音频质量的下降。
问候
本
以上来自于谷歌翻译
以下为原文
If you're delivering Windows 10 as your VM OS, then you need nothing less than 1GB of FrameBuffer
As your user count and density are directly tied to your vGPU profiles, you do need an accurate count of how many users you plan to move on to the system. Otherwise, you will either under-spec everything, meaning that you will need to purchase more individual servers as they won't be a sufficient specification, or you will over spec them, and have wasted resources. You do need to be more accurate with your numbers than just saying "around 50 to 100". Also, what about the rest of your infrastructure? Have you considered the additional storage I/O and network bandwidth? ... when adding 50 - 100 users who are working with video, you need to consider all resources.
It's not a theory, it's a fact :-) Don't look at individual component prices, look at the cost of the whole system. The more users that can share the same resource, the more cost effective the entire system becomes, and that's one of the main reasons we virtualise (and the ENTIRE reason that NVIDIA GRID even exists!); to get better resource utilisation, ultimately, because it ends up being cheaper overall than giving users their own dedicated hardware. It's not just about the physical server; Rack Space, Power, Cooling, Licensing, Support, Maintenance, Upgrades, Updates etc etc. It all costs money.
The higher the server density, the more cost effective the system is to implement and support.
You didn't ask for a performance comparison between the M10 and M60, you asked whether the M60 was worth twice the purchase price of a K2, to which the answer was, (in a little more detail) there's more to it than unit purchase price. The M60 is obviously more powerful than the M10, however the M10 trades performance for density. Based on FrameBuffer, the M60 will support 50% less users than the M10. This is where you need to know how many users you plan to add to the system, so you can spec and design appropriately.
Let's say you have 64 users total (that falls within the "around 50 - 100" bracket):
If you have up to 32 users per server, I would say buy 2x M60s for each server and give them a 1GB vGPU profile each. The reason for that, is that the M60 has more H.264 streams than the M10 (36 vs 28), and as you plan to deliver video, this is an important consideration. If you want to add more users on to the system, you now need to factor in what I mentioned above about cost vs value. You now need to purchase additional server resource to support the additional user density. Also, if you have less users on a server, you need less CPU and RAM to support them; this is money that could be used to offset additional server resource to support more users.
Let's say you have 65+ users total (that exceeds the M60s FrameBuffer capacity with 2 servers):
For more than 32 users per server with a 1GB vGPU profile, you will need to use the M10. The M10 will do the job, however if all users on the same server start viewing videos at the same time, you may well start to suffer reduced performance. Remembering that once users are connected, you can't load balance VMs between hosts (however you will be able to later this year / next year ...).
Also, your server density will depend on your CPU and RAM specifications, which you haven't mentioned yet.
With all of that said, if you only have 2x new servers and want to support more than 64 users, a pair of M10s in each server is your only option, as the M60s simply don't have the FrameBuffer capacity to support more than 64 users.
You need a Thin Client that has H.264 decode capability. Typically something with a SOC (System on Chip) or dedicated GPU will have that capability. A "Raspberry Pi" will be the cheapest option, then you're in to many different choices. Intel NUCs make great Thin Clients, and there are a lot of different models to choose from and if you don't need the latest and most powerful, they are also pretty cheap as well. The Thin Client is still a very important part of the system. Poor Thin Client choice can destroy a perfectly designed back end system due to the user experience, so make sure you test various vendor brands / models and validate them properly. And don't underestimate what's required to stream a video to an acceptable level. As I've mentioned to someone else who posted on here recently, I personally think streaming videos is one of the hardest things to do, as it requires near perfect visuals and audio at all times. Any drops in visual quality or frame rate are immediately visible to the person viewing the video, where as someone using Outlook or typing a document, may not notice a drop in visual or audio quality.
Regards
Ben
如果您将Windows 10作为VM OS提供，那么您需要不超过1GB的FrameBuffer
由于您的用户数和密度与您的vGPU配置文件直接相关，因此您需要准确计算您计划移动到系统的用户数。
否则，您将要么低估一切，这意味着您将需要购买更多的单个服务器，因为它们不是一个足够的规范，或者您将过度规范它们，并浪费资源。
你需要对你的数字更准确，而不仅仅是说“大约50到100”。
另外，您的其他基础设施呢？
您是否考虑过额外的存储I / O和网络带宽？
...当添加50-100个使用视频的用户时，您需要考虑所有资源。
这不是一个理论，它是一个事实:-)不要看单个组件价格，看看整个系统的成本。
可以共享相同资源的用户越多，整个系统的成本效率就越高，这也是我们虚拟化的主要原因之一（以及NVIDIA GRID甚至存在的整体原因！）;
最终，为了获得更好的资源利用率，因为它总体上比为用户提供他们自己的专用硬件更便宜。
它不仅仅与物理服务器有关;
机架空间，电源，冷却，许可，支持，维护，升级，更新等等都需要花钱。
服务器密度越高，系统实施和支持的成本效率就越高。
你没有要求M10和M60之间的性能比较，你问M60是否值得K2的购买价格的两倍，答案是，（更详细一点）它比单位购买更多
价钱。
M60显然比M10更强大，但是M10的密度表现更好。
基于FrameBuffer，M60将比M10支持少50％的用户。
您可以在此处了解计划添加到系统的用户数量，以便进行适当的规范和设计。
假设您总共有64个用户（在“约50 - 100”范围内）：
如果每个服务器最多有32个用户，我会说为每个服务器购买2个M60，并为每个服务器提供1GB的vGPU配置文件。
原因在于，M60拥有比M10更多的H.264流（36对28），并且当您计划提供视频时，这是一个重要的考虑因素。
如果您想在系统上添加更多用户，您现在需要考虑我上面提到的有关成本与价值的因素。
您现在需要购买额外的服务器资源以支持额外的用户密度。
此外，如果服务器上的用户较少，则需要较少的CPU和RAM来支持它们;
这是可用于抵消额外服务器资源以支持更多用户的资金。
假设您有超过65个用户（超过M60s FrameBuffer容量和2台服务器）：
对于具有1GB vGPU配置文件的每台服务器超过32个用户，您将需要使用M10。
M10将完成这项工作，但如果同一服务器上的所有用户同时开始观看视频，您可能会开始降低性能。
请记住，一旦用户连接，您就无法在主机之间对VM进行负载平衡（但是您可以在今年/明年之后进行...）。
此外，您的服务器密度将取决于您尚未提及的CPU和RAM规格。
尽管如此，如果您只有2个新服务器并且想要支持超过64个用户，那么每个服务器中的一对M10是您唯一的选择，因为M60只是没有FrameBuffer容量来支持超过64个
用户。
您需要具有H.264解码功能的瘦客户端。
通常，具有SOC（片上系统）或专用GPU的东西将具有该功能。
“Raspberry Pi”将是最便宜的选择，然后你会有很多不同的选择。
英特尔NUC制造出极佳的瘦客户机，有很多不同的型号可供选择，如果你不需要最新和最强大的，它们也很便宜。
瘦客户端仍然是系统中非常重要的一部分。
由于用户体验不佳，瘦客户机选择可能会破坏设计完美的后端系统，因此请确保您测试各种供应商品牌/型号并正确验证它们。
并且不要低估将视频流式传输到可接受级别所需的内容。
正如我最近在这里发布的其他人所提到的，我个人认为流媒体视频是最难做的事情之一，因为它需要随时提供近乎完美的视觉效果和音频。
观看视频的人立即可以看到视觉质量或帧速率的任何下降，其中使用Outlook或键入文档的人可能不会注意到视觉或音频质量的下降。
问候
本
以上来自于谷歌翻译
以下为原文
If you're delivering Windows 10 as your VM OS, then you need nothing less than 1GB of FrameBuffer
As your user count and density are directly tied to your vGPU profiles, you do need an accurate count of how many users you plan to move on to the system. Otherwise, you will either under-spec everything, meaning that you will need to purchase more individual servers as they won't be a sufficient specification, or you will over spec them, and have wasted resources. You do need to be more accurate with your numbers than just saying "around 50 to 100". Also, what about the rest of your infrastructure? Have you considered the additional storage I/O and network bandwidth? ... when adding 50 - 100 users who are working with video, you need to consider all resources.
It's not a theory, it's a fact :-) Don't look at individual component prices, look at the cost of the whole system. The more users that can share the same resource, the more cost effective the entire system becomes, and that's one of the main reasons we virtualise (and the ENTIRE reason that NVIDIA GRID even exists!); to get better resource utilisation, ultimately, because it ends up being cheaper overall than giving users their own dedicated hardware. It's not just about the physical server; Rack Space, Power, Cooling, Licensing, Support, Maintenance, Upgrades, Updates etc etc. It all costs money.
The higher the server density, the more cost effective the system is to implement and support.
You didn't ask for a performance comparison between the M10 and M60, you asked whether the M60 was worth twice the purchase price of a K2, to which the answer was, (in a little more detail) there's more to it than unit purchase price. The M60 is obviously more powerful than the M10, however the M10 trades performance for density. Based on FrameBuffer, the M60 will support 50% less users than the M10. This is where you need to know how many users you plan to add to the system, so you can spec and design appropriately.
Let's say you have 64 users total (that falls within the "around 50 - 100" bracket):
If you have up to 32 users per server, I would say buy 2x M60s for each server and give them a 1GB vGPU profile each. The reason for that, is that the M60 has more H.264 streams than the M10 (36 vs 28), and as you plan to deliver video, this is an important consideration. If you want to add more users on to the system, you now need to factor in what I mentioned above about cost vs value. You now need to purchase additional server resource to support the additional user density. Also, if you have less users on a server, you need less CPU and RAM to support them; this is money that could be used to offset additional server resource to support more users.
Let's say you have 65+ users total (that exceeds the M60s FrameBuffer capacity with 2 servers):
For more than 32 users per server with a 1GB vGPU profile, you will need to use the M10. The M10 will do the job, however if all users on the same server start viewing videos at the same time, you may well start to suffer reduced performance. Remembering that once users are connected, you can't load balance VMs between hosts (however you will be able to later this year / next year ...).
Also, your server density will depend on your CPU and RAM specifications, which you haven't mentioned yet.
With all of that said, if you only have 2x new servers and want to support more than 64 users, a pair of M10s in each server is your only option, as the M60s simply don't have the FrameBuffer capacity to support more than 64 users.
You need a Thin Client that has H.264 decode capability. Typically something with a SOC (System on Chip) or dedicated GPU will have that capability. A "Raspberry Pi" will be the cheapest option, then you're in to many different choices. Intel NUCs make great Thin Clients, and there are a lot of different models to choose from and if you don't need the latest and most powerful, they are also pretty cheap as well. The Thin Client is still a very important part of the system. Poor Thin Client choice can destroy a perfectly designed back end system due to the user experience, so make sure you test various vendor brands / models and validate them properly. And don't underestimate what's required to stream a video to an acceptable level. As I've mentioned to someone else who posted on here recently, I personally think streaming videos is one of the hardest things to do, as it requires near perfect visuals and audio at all times. Any drops in visual quality or frame rate are immediately visible to the person viewing the video, where as someone using Outlook or typing a document, may not notice a drop in visual or audio quality.
Regards
Ben
举报
