![pcoip protocol cisco pcoip protocol cisco](https://tblogbelgium.files.wordpress.com/2011/12/setup.jpg)
When you moved the drawing the text in the drawing couldn’t keep up it seemed. From time to time with PcoIP it seemed that something was “hanging”, like someone is using all the resources and you have to wait. with PCoIP even when testing over a LAN it was just not smooth enough for them. When working with PCoIP the lagging is noticed more than with e.g.
![pcoip protocol cisco pcoip protocol cisco](https://stringfixer.com/files/141355741.jpg)
The reason I was asked on-premises was that they experienced lagging when moving in the drawing or moving the drawing. The last test was about the user experience, of course a screenshot won’t do here so I will explain in writing what we noticed. When we disable H.264 with Blast we noticed a near perfect line again, so H.264 had an effect on the way the lines are constructed. The further you zoom in the worse the line got. The line seems to be made up out of small blocks or something like it. With blast and H.264 enabled we see that the colour of the line is darkener and that the line starts to break up. With HTML Access we see the same result as with PCoIP, the lines are sharp. This is how the drawing should look like. With PCoIP the lines are sharp, no questions asked. These guys are using AutoCad and they need sharp lines no matter how far you zoom in. Next we zoomed in on the letter ‘a’ so we could see how sharp the line really is. PCoIP comes second, the brightness of the drawing with PcoIP is very good, like the colours give light. Blast H.264 disabledįrom the test we concluded that Blast without H.264 enabled and HTML access where the best performing protocols, the colours and sharpness of the drawing was perfect. also here we noticed that compared to PCoIP the drawing wasn’t that clear. So H.264 has effect on the look and feel of the desktop. The colours are flying of the screen and it is super sharp. The last test in this scenario was Blast with H.264 disabled. As you can see instantly the lines are blurred and the whole picture is not that smooth anymore. Next up was Blast, first with H.264 encoding enabled. There is almost no difference between the looks of PCoIP and HTML access at this level but looking at the whole drawing there is a degradation, not much but you see a difference. as you can see the colours are nearly identical it looks fine. PCoIPĪfter this test we switched to HTML access and connected to the same desktop with the same drawing over the same network. Below you see the PCoIP example, clear text and lively colours. The first test we did was zoom in on his desk and see how lively the colours are and if the text and lines are clear. You can do this same test as well, we used the demo floor plan drawing in AutoCad 2017 and zoomed in on Carl Benard sitting at desk 6023. The test consist of a AutoCad desktop with 4vCPU’s and 8GB RAM running WindLTSB.
![pcoip protocol cisco pcoip protocol cisco](https://docplayer.net/docs-images/39/19384364/images/1-0.png)
Blast would work over UDP and that encoding wasn’t done with PNG. We applied several policies to make sure that e.g.
Pcoip protocol cisco series#
To verify the customer finding we did a series of tests. They can reproduce the hanging so I set off to do test and see if we can find a reason behind this. Lagging is seen only in AutoCad, as well as the hanging that occurs rarely. The issue they experience is that PCoIP is lagging at some moments and seems to hang occasionally. Smart policies in UEM at High speed lan.PCoIP, Frame rate at 40, changed it to 60.Some extra information, PCoIP is tuned a bit but we are looking at more tuning.
![pcoip protocol cisco pcoip protocol cisco](https://www.cisco.com/c/dam/en/us/td/docs/unified_computing/ucs/UCS_CVDs/ucs_flashstack_vmware_horizon8_vsphere70.docx/_jcr_content/renditions/ucs_flashstack_vmware_horizon8_vsphere70_244.jpg)
Pcoip protocol cisco windows#
We did the tests on a Windows devices for this blog to be able to test other protocols.
Pcoip protocol cisco windows 10#
the clients they use are a mix of Windows 10 clients and zero clients HP T310. The environment runs fine, they have one office where most people are working. The customer is an Architectural agency who is using AutoCad 2017. The environment consists of a VMware Horizon View 7.0.3 environment with Microsoft WindLTSB. We are not finished yet as we seek for the best protocol for this scenario, none of them were perfect, yet. I took a look at the environment and we discussed the differences as we tested the protocols. Today I took a look at a real life scenario where a customer had a question about user experience for their Horizon environment. Blast for instance has the ability to work over UDP offering better performance, HTML access is not capable of using UDP. Although blast and HTML have similarities there are differences. For a browser only scenario HTML access is available. Blast of course is the protocol they’ve been pushing more and more. PCoIP and Blast being the ones we use with customers. VMware has a number of protocols available with VMware Horizon product. VMware protocols, Blast vs HTML access vs PCoIP, real life scenario