How to adjust webRDP compression in 126.96.36.199 and higher.
WebRDP utilizes a technology which compresses RDP traffic into a PNG image format. A default value has been set to provide both good compression and network payload size. WebRDP supports adjusting this compression level. If the desired effect is to increase compression, thereby decreasing network payload size, then set the level to 9. If the effect is to increase server performance, lowering compression, thereby increasing network payload size, then set the value to 1. The trade off to consider is server CPU load: a higher compression utilizes more processing. More processing slows down server CPU performance and load capacity.
Here are the following compression levels,
1 – best speed (lower compression, larger network payload, lower CPU load)
4 - default
9 – best size (higher compression, smaller network payload, higher CPU load)
Which do I choose? If the system default is not adequate, then you can adjust the level. Consider these factors,
- Low bandwidth, low volume – best size will help
- High bandwidth, high volume – best speed will help
- Low bandwidth, high volume – somewhere in the middle, leaning toward best size will help
- High bandwidth, low volume – somewhere in the middle, leaning toward best speed will help
The compression levels can be changed via the webRDP.properties file. A sample file is attached to this document and you can edit that and put in the /webRDP-Gateway/license directory. Stop and restart the webRDP system to make it take effect. To use the standard Java compression (non-optimized) set the value to 0 or to anything but 1-9.