The default configuration of CoreXL Firewall instances and the CoreXL SNDs might not be optimal for your needs.
If the default number of CoreXL SNDs is not enough to process the incoming traffic, and your Security Gateway computer contains enough CPU cores, you can reduce the number of CoreXL Firewall instances. This automatically allocates additional CPU cores to run the CoreXL SNDs.
This scenario is likely to occur if much of the traffic is accelerated by SecureXL. In this case, the task load of the CoreXL SNDs may be disproportionate to that of the CoreXL Firewall instances.
To check if the SND is slowing down the traffic:
Step |
Description |
---|---|
1 |
Identify the processing CPU core, to which the interfaces direct their traffic:
|
2 |
Under heavy traffic conditions, run the Examine the values for the different CPU cores in the ' |
We recommend to allocate an additional CPU core to the CoreXL SND only if all these conditions are met:
top
command, the 'idle
' values for the CPU cores that run the CoreXL SNDs are in the 0%-5% range.top
command, the sum of the 'idle
' values for the CPU cores that run the CoreXL Firewall instances is significantly higher than 100%.If at least one of the above conditions is not met, the default CoreXL configuration is sufficient.
To allocate an additional processing CPU core to the CoreXL SND:
Item |
Description |
---|---|
1 |
Reduce the number of CoreXL Firewall instances in the |
2 |
|
3 |
Reboot to apply the new configuration. |