For display traffic, many elements can affect network bandwidth, such as protocol used, monitor resolution and configuration, and the amount of multimedia content in the workload. Concurrent launches of streamed applications can also cause usage spikes.

Because the effects of these issues can vary widely, many companies monitor bandwidth consumption as part of a pilot project. As a starting point for a pilot, plan for 150 to 200Kbps of capacity for a typical knowledge worker.

With the PCoIP display protocol, if you have an enterprise LAN with 100Mb or a 1Gb switched network, your end users can expect excellent performance under the following conditions:

Two monitors (1920x1080)

Heavy use of Microsoft Office applications

Heavy use of Flash-embedded Web browsing

Frequent use of multimedia with limited use of full screen mode

Frequent use of USB-based peripherals

Network-based printing

This information was excerpted from the information guide called PCoIP Display Protocol: Information and Scenario-Based Network Sizing Guide.

If you use the PCoIP display protocol from VMware, you can adjust several elements that affect bandwidth usage.

You can adjust the size of the image cache on Windows and Linux client systems, from 50MB to 300MB. Image caching reduces the amount of display data that must be retransmitted.

You can configure the image quality level and frame rate used during periods of network congestion. The quality level setting allows you to limit the initial quality of the changed regions of the display image. Unchanged regions of the image progressively build to a lossless (perfect) quality. You can adjust the frame rate from 1 to 120 frames per second.

This control works well for static screen content that does not need to be updated or in situations where only a portion needs to be refreshed.

You can also turn off the build-to-lossless feature altogether if instead of progressively building to perfect quality (lossless), you choose to build to perceptual lossless.

You can control which encryption algorithms are advertised by the PCoIP endpoint during session negotiation. By default, both Salsa20-256round12 and AES-128-GCM algorithms are available.

With regard to session bandwidth, you can configure the maximum bandwidth, in kilobits per second, to correspond to the type of network connection, such as a 4Mbit/s Internet connection. The bandwidth includes all imaging, audio, virtual channel, USB, and control PCoIP traffic.

You can also configure a lower limit, in kilobits per second, for the bandwidth that is reserved for the session, so that a user does not have to wait for bandwidth to become available. You can specify the Maximum Transmission Unit (MTU) size for UDP packets for a PCoIP session, from 500 to 1500 bytes.

You can specify the maximum bandwidth that can be used for audio (sound playback) in a PCoIP session.