Last Modified: Jun 10, 2021
See more info
Known Affected Versions:
13.0.0, 13.0.0 HF1, 13.0.0 HF2, 13.0.0 HF3, 13.0.1, 13.1.0, 184.108.40.206, 220.127.116.11, 18.104.22.168, 22.214.171.124, 126.96.36.199, 188.8.131.52, 184.108.40.206, 220.127.116.11, 13.1.1, 18.104.22.168, 22.214.171.124, 126.96.36.199, 188.8.131.52, 13.1.3, 184.108.40.206, 220.127.116.11, 18.104.22.168, 22.214.171.124, 126.96.36.199, 188.8.131.52, 13.1.4, 184.108.40.206
Opened: Nov 01, 2016
When deploying large number of DoS profiles with Bot signatures enabled on low-end platforms, the memory spills over to the swap area. Each DoS profile consumes about 2 MB of memory per core for accommodating the complied bot signatures. For example, on VE with 2 cores and 8 GB of memory, deploying 1024 DoS profiles with bot signatures will consume 4 GB which together with the other memory requirements of ASM far exceeds the physical memory. The symptom is high utilization of swap memory.
Severe performance degradation.
Deploy large number (over 100) of DoS profiles with Bot signatures.
On VE platforms, provision at least 4 GB more memory to the VM. On vCMP platform, assign this amount of memory to the guest machine. On physical machines, the only option is to upgrade to a larger memory platform. Consider using less profiles by reusing the same DoS profile on more than one Virtual Server.