NOTE: In order for the agent to connect to the server, the following ports need to be open on the VM in Azure So I was curious to see how it worked on Azure with the N-series and support for Windows Server 2016, since the Azure datacenters are not located anywhere close to the nordics, it is crucial to have a remote display protocol which are able to leverage the GPU and deliver the best end-user experience without causing any huge overhead on the server, and of course being able to use it without having a large Azure infrastructure. PCoIP has some good ways of sending reliable data, for instance USB packets are always reliable, dropped image packets are resent only if they have not been written over by a subsequent display update (so, for instance Heaven benchmark which is part of the video clip further down below, almost never since it is constantly updating the screen), and audio packets are too latency sensitive to retransmit, so PCoIP uses forward error correction (FEC) to correct missing audio packets and never retransmit dropped audio packets. Also most UDP based remote protocols use MTU of 1200, to ensure that there is no fragmentation of packets during transmission. That means that Teradici has to provide that within the PCoIP protocol itself, which might translate into “artifacts” when working on the workstation. Now the downside with using UDP is that it does not have any form of reliable transport. Now I have previously tested PCoIP vs for instance TCP Blast –> just to compare TCP Blast which is by default TCP and PCoIP which is based upon using UDP. Teradici are the creators behind the PCoIP protocol, which its often leveraged in VMware Horizon View and supported by multple thin client vendors, which in most cases are also leveraging a Teradici SOC (System on a chip) which provides a hardware decode of the pixel stream enabling faster frame rates and highly secure, simple to manage updates. Earlier this year, Microsoft announced that they were partnering with Teradici on their N-series virtual machine instances in Azure, which I’ve blogged about previously here –>
0 Comments
Leave a Reply. |