There is a need to test the speed throughput of Kerio Control in the environment to ensure that their Kerio Control configuration is not limiting the internet connectivity speed.
Guidelines for Running Effective Speed Tests
- Make sure that any other intensive bandwidth utilization application is not using Kerio Control.
- Ensure that the PC where you are performing the speed test meets the following criteria:
- It is connected via wire to Kerio Control.
- It has adequate resources, especially CPU. Consumption should be low without the speed test.
- Disable Debug logs on Kerio Control.
- Repeat the test a couple of times changing the test server (select a physically nearby server). Ideally, repeat the test at different times of the day as the results can vary based on external factors.
Elements That Can Affect Kerio Control
- Number of Rules
- Debug logging
- Size of files being transferred
- Services that are enabled
- Type of Internet Connectivity
- Custom Bandwidth rules and QoS
Kerio Control is not simply a Firewall but a UTM (Unified Threat Management System). Hence it has additional built-in features like AntiVirus Engine, IPS System, Web Filter, Content Filter, Anti-Spoofing, etc.
As a lot of inspections are done at each of these layers, usually there would be a drop of 25% to 30% in the internet speeds. So it can be assumed as normal behavior if the internet speeds are reduced by 20% to 30% after passing through Kerio Control.
If the speeds deteriorate beyond 50%, then it is abnormal and needs to be investigated and reported to Engineering after initial troubleshooting by Customer Support.