GRID K1 Windows 10大小怎么调整

这是受支持的配置还是仅用于测试目的？



以下为原文

Is this a supported configuration or is this just for testing purposes only?

本文档的第4页说两台显示器都应该使用K120Q配置文件：
http://images.nvidia.com/content/grid/pdf/GRID-vGPU-User-Guide.pdf
所以不应该修改驱动程序。
此外，在生产环境中既不支持也不建议修改驱动程序。



以下为原文

Page 4 of this document says that both monitors should work with the K120Q profile:


http://images.nvidia.com/content/grid/pdf/GRID-vGPU-User-Guide.pdf


So there should be no need to modify the driver. Also, modifying the driver is neither supported or recommended in a production environment.

嗨本，
不幸的是，这对Windows 10无效。有一个单独的Messagebox表明我们不支持512MB和Windows 10的双显示器：
*剪断*
帧缓冲区小于1 GB的GRID vGPU仅支持1个虚拟显示头
在Windows 10客户操作系统上。
*剪断*
问候
西蒙



以下为原文

Hi Ben,

unfortunately this is not valid for Windows 10. There is a seperate Messagebox indicating that we don't support Dual Monitor for 512MB and Windows 10:

*snip*
GRID vGPUs with less than 1 Gbyte of frame buffer support only 1 virtual display head
on a Windows 10 guest OS.
*snip*

Regards

Simon

感谢西蒙的抬头，非常感谢......发现它（第7页）。
在这种情况下，要纠正我上面的帖子......不，没有一种支持的方法来规避司机。
如果您想将W10与多显示器配合使用，则需要使用至少1GB帧缓冲的配置文件
问候
本



以下为原文

Thanks for the heads up Simon, much appreciated ... Found it (Page 7).

In that case, to correct my post above ... No, there isn't a supported way to circumvent the driver. You'll need to use a profile with at least 1GB of Frame Buffer if you'd like to use W10 with multi-monitor

Regards

Ben

我的观点基于我的发现：
Microsoft Windows 10新增“合成窗口管理器”（DWM.exe）问题：
它是三重缓冲管理器（Win7“Aero”是双缓冲区） - >这导致更多的GPU内存需求和更高的VDI延迟
它有一些嵌入式“优化”（问题仍然存在于Win7中） - >这会导致VDI的不可预测性和低FPS（https://gridforums.nvidia.com/default/topic/1149/xendesktop-with-nvidia-grid/
3D-负载影响-nvenc性能/后/ 4247/4247＃）
通过扩展非主要监视器输出（https://medium.com/@toncijukic/windows-10-desktop-compositor-and-high-ppi-rendering-7fa29c4cc18a），它正在瘫痪。
它不能被禁用！
NVidia GPU / vGPU驱动问题：
NVidia视频编解码器SDK（对于大多数“现代”协议（“Blast Extreme”/“HDX 3D Pro”），需要“本地”硬件加速编码到h264用于VDI流，这对于每个流具有令人难以置信的GPU内存要求260MB（你
需要两个用于双监视器，期望16 *帧缓冲区大小~14BMB用于FullHD）（https://devtalk.nvidia.com/default/topic/1006545/260m-gpu-memory-usage-for-one-gpu-h264-video
-decoder-是-正 -  /）
NVidia Capture SDK与DWM配合使用非常糟糕（如https://gridforums.nvidia.com/default/topic/1046/nvidia-grid-apis/fullscreen-video-capture-issue/）
vGPU 512MB配置文件允许在guest虚拟机中仅使用436207616个字节（framebufferlength = 0x1A000000和reserved_fb = 0x6000000伪造/隐藏虚拟化丢失）（请参阅https://gridforums.nvidia.com/default/topic/438/xendesktop-with-nvidia-
网格/ k220q视频-RAM-xenserver的-6-5 /后/ 1922 /＃1922）。
驱动程序在低GPU内存情况下随机崩溃！
来自NVidia的解决方案 - 禁用对512MB vGPU配置文件的双监视器支持，并从Pascal vGPU中删除512MB配置文件，并忽略所有其他问题。
我根据我的真实编程实验仅描述了我的观点，并且我不试图干涉NVidia的Visions。



以下为原文

My opinion based on my findings:

Microsoft Windows 10 new "Compositing window manager" (DWM.exe) problems:

• it is triple-buffer manager (Win7 "Aero" was double-buffer) -> this leads to more GPU memory requirement and higher latency for VDI
  
• it has some embedded "optimization" (the problem persists from Win7) ->  this leads to unpredictable and low FPS for VDI (https://gridforums.nvidia.com/default/topic/1149/xendesktop-with-nvidia-grid/3d-load-impacts-nvenc-performance/post/4247/#4247)
  
• it is crippling by scaling non-primary monitor outputs (https://medium.com/@toncijukic/windows-10-desktop-compositor-and-high-ppi-rendering-7fa29c4cc18a).
  
• it cannot be disabled !
  

NVidia GPU/vGPU driver problems:

• NVidia Video Codec SDK (this is needed by "local" HW accelerated encoding to h264 for VDI stream for most "modern" protocols ("Blast Extreme"/"HDX 3D Pro")) has unbelievable GPU memory requirements 260MB per one stream (you need two for dualmonitor, expecting 16*frame buffer size ~ 14MB for FullHD) (https://devtalk.nvidia.com/default/topic/1006545/260m-gpu-memory-usage-for-one-gpu-h264-video-decoder-is-normal-/)
  
• NVidia Capture SDK works badly with DWM (like https://gridforums.nvidia.com/default/topic/1046/nvidia-grid-apis/fullscreen-video-capture-issue/)
  
• vGPU 512MB profile allows to use ONLY 436207616 bytes in guest (framebufferlength=0x1A000000 and reserved_fb=0x6000000 to fake/hide virtualization lost) (see https://gridforums.nvidia.com/default/topic/438/xendesktop-with-nvidia-grid/k220q-video-ram-xenserver-6-5/post/1922/#1922).
  
• driver randomly crashes in low GPU memory situation !
  

Solution from NVidia - disable dualmonitor support for 512MB vGPU profiles and remove 512MB profiles form Pascal vGPU and ignore all other problems.
I described only my point of view based on my real programming experiments and I do not try to interfere with NVidia's Visions.

哇谢谢你非常彻底的答案！
这确实是一些可靠的信息。
基本上，当从Windows 7升级到Windows 10时，我们需要确保我们依靠32台桌面，而不是每M10 64台，因为营销幻灯片建议......
那么512 MB配置文件是否适用于未来，特别是当它已经从基于Pascal的设置中删除时？
根据这些信息，我不再真正看到这个用例，除非有人未来使用Windows 10，这似乎不太可能。
@mcerveny：你介意我把这些信息写成博客吗？
对很多人来说似乎非常非常有趣！



以下为原文

Wow thanks for the very thorough answers! That is some solid information indeed. Basically, when upgrading from windows 7 to windows 10, we need to make sure we count on 32 desktops and not 64 per M10, as marketing slides suggest...

Is the 512 MB profile even viable for the future then, especially when it is already removed from the Pascal based setups? I don't really see a use case for that anymore in light of this information, except if someone does not go and use Windows 10 in the future, which seems unlikely.

@mcerveny : would you mind if I take this information and write a blog about it? Seems very, very interesting to a lot of people!

我的想法：
Iff你不使用带有硬件h264编码的“Blast Extreme”/“HDX 3D Pro”，并且只使用SW h264 / jpeg / png（是的，你在协议设置中丢失了至少一个用于编码每个streeam的CPU）（或pcoip）
可以启用第二个监视器没有问题（#NotSupported）。
卡上使用“本地”HW h264编码器会有更多设计错误/失败。
编码器无法在所有VDI上进行全硬件加速（请参阅https://gridforums.nvidia.com/default/topic/823/tesla-m10/） - 在1xK1上，您只能使用~16 FHD h264流，而在1xM10上您只能使用
只能使用~28 FHD h264流（不是64，因为双显示器不是128）。
即使使用Pascal芯片也不是更好。
我根据我的真实编程实验仅描述了我的观点，并且我不试图干涉NVidia的Visions。
等待NVidia工程师（https://gridforums.nvidia.com/default/topic/823/grid-boards/tesla-m10/post/2942/#2942）或NGCA（http：// www。
nvidia.com/object/grid-advisory-council.html）。
我最小化了我在这个论坛上的帖子。
#NotSupported  - 第一条不支持的规则是你不谈论不支持。
下一个不支持的规则是你不解释原因。
下一个不支持的规则是......规则被破坏了！



以下为原文

My opinion:
Iff you do not use "Blast Extreme"/"HDX 3D Pro" with HW h264 encoding and use only SW h264/jpeg/png (yes you lost at least one CPU for encoding per streeam) (or pcoip) in your protocol setup you can probably enable second monitor without problems (#NotSupported).
There is more design errors/fails with using "local" HW h264 encoder on card. The encoder is incapable for full HW acceleration on all VDI (see https://gridforums.nvidia.com/default/topic/823/tesla-m10/) - on 1xK1 you can use only ~16 FHD h264 streams and on 1xM10 you can use only ~28 FHD h264 streams (not 64 and of cause not 128 for dual monitor). It is not better even with Pascal chips.



I described only my point of view based on my real programming experiments and I do not try to interfere with NVidia's Visions. Wait for better answer/explanation from NVidia engineers (https://gridforums.nvidia.com/default/topic/823/grid-boards/tesla-m10/post/2942/#2942) or NGCA (http://www.nvidia.com/object/grid-advisory-council.html). I minimize my posting on this forum.

#NotSupported - The first rule of Not Supported is you don't talk about Not Supported. The next rule of Not Supported is you don't explain why. The next rule of Not Supported is ... Rules are made to be broken!

嗨mcerveny，
感谢您的输入。
首先，由于禁用了512MB配置文件，因此无法在512MB配置文件上使用NVENC。
你已经提到了可能的原因。
但是你引用的数字（1个HD流的260MB）是很高的。
实际上我们谈的是80-100MB。
此外，我们需要了解幻灯片中可能的给定H264流应该只是给出一种示例。
在我的幻灯片中，我更喜欢真正的编码性能而不是流的数量，因为这会产生误导。
我们来看看M10的例子：
我们有4个编码器，每个210fs，所以我们可以提供4x7xFullHD @ 30fps。
从理论上讲，我们可以使编码器过载，因为我们在M10上获得了32个具有1GB配置文件的VM。
但请记住，现实看起来不同。
M10用例是办公室工作人员，我没有看到一个客户同时运行28流FullHD和30fps。
真正的3D用例看起来不同，但是我们在M60上为16个用户提供了36个流，这意味着每个用户都可以以30fps运行2xFullHD。
这是一个更详细的编码/解码数据表：
https://developer.nvidia.com/video-encode-decode-gpu-support-matrix
问候
西蒙



以下为原文

Hi mcerveny,

thanks for your input. First of all there is no option to use NVENC on the 512MB profile as it is disabled.
You already mentioned possible reasons. But the numbers you're referencing (260MB for 1 HD stream) are way to high. We talk about 80-100MB in reality.
In addition we need to understand that the given H264 streams possible in our slides should just give a kind of example. In my slidedecks I prefer the real encoding performance instead of number of streams as this is misleading.
Let's take the M10 example:
We have 4 encoders with 210fs each so we could deliver 4x7xFullHD@30fps. In theory we could overload the encoder as we get 32 VMs with 1GB profile on a M10. But keep in mind that the reality looks different. M10 use case is office workers and I've not seen a single customer running 28 streams FullHD with 30fps simultaniously. Real 3D use case looks different but here we have 36streams on M60 for 16 users which means every user could run 2xFullHD with 30fps.
Here is a more detailed datasheet for encoding/decoding:

https://developer.nvidia.com/video-encode-decode-gpu-support-matrix


Regards

Simon

是的，“本地”编码器也是如此。
我正在使用“远程”编码器来解决这个问题。
不完全正确。
这取决于“API”和“maxresolution”。
我为第一个FHD测量了148MB GPU内存。
如果有可能改变分辨率并且你不能重新启动整个解码器而不是maxEncodeWidth / maxEncodeHeight应该被设置为最大支持的分辨率（例如2560x1600或4096x2160）并且你获得更高的内存分配（例如，对于第一流甚至FHD，213MB或393MB）。
请务必小心参考这个不正确的文件（https://devtalk.nvidia.com/default/topic/1019670/?comment=5191551）。
此致，马丁



以下为原文


Yes, it is true for "local" encoder. I am using "remote" encoder to resolve this problems.


Not completely true. It depends on "API" and "maxresolution". I measured 148MB GPU memory for first FHD. If there is possibility to change resolution and you cannot restart whole decoder than maxEncodeWidth/maxEncodeHeight should be set to maximum supported resolution (eg. 2560x1600 or 4096x2160) and you get higher memory allocation (eg. 213MB or 393MB for first stream even FHD).


Be very careful to refer this incorrect document (https://devtalk.nvidia.com/default/topic/1019670/?comment=5191551).

Regards, Martin