RES Workspace Manager 2014 is used all over the world in the most diverse and complex network environments; from companies with expensive vlans running across borders to companies with many employees running on 3g networks. For customers who deploy RES Workspace Manager 2014 in these environments especially, we are introducing compression for transactions from the RES Workspace Manager agent to the relay server in RES Workspace Manager 2014 SR2.
We know how important it is to keep track and minimize the network traffic that is running from the RES Workspace Manager 2014 SR2 agents to the relay servers. Therefore, we compress the data before sending it from the agent to the relay servers in RES Workspace Manager 2014 SR2.
Now, I hear you asking, “Is this really going to help my users?” That is what I will clarify in this post.
We chose to enable this functionality by default because it has minimum impact on the server CPU and client CPU. We tested this extensively in our lab environment. In the example below, you can see the results of the network data with and without compression.
For testing this functionality, we wrote the scenario below. In this case, the test ran on a Microsoft Azure setup, which consisted of a device with Windows Server 2008 R2 connected to Relay Server and a configured, relatively large cache.
In the table above you can see the difference between the compressed and uncompressed data of running the scenario description 5 times as described earlier.
As you can see, the amount of data (in kilobytes) with compression is reduced by 38%.
As a result, especially in larger and more complex environments, we foresee a huge improvement in bandwidth consumption. If you want to learn more about RES Workspace Manager 2014 SR2, you can visit support.ressoftware.com and follow RES Workspace Manager on this blog.