Description
On FortiGate the WAD daemon is used to perform explicit proxy tasks.
With release 5.0, FortiGate is limited to a single WAD process regardless of the number of available CPUs.
With release 5.2, the limitation was removed and multiple WAD processes can be used in parallel. The number of WAD process that can run in parallel depends on hardware and configuration.
Examples:
FortiGate 3600C: between 1 and 32 WAD process, default 16.
FortiGate 500D: between 1 and 4 WAD process, default 2.
FortiGate 100D: between 1 and 4 WAD process, default 2.
With release 5.0, FortiGate is limited to a single WAD process regardless of the number of available CPUs.
With release 5.2, the limitation was removed and multiple WAD processes can be used in parallel. The number of WAD process that can run in parallel depends on hardware and configuration.
Examples:
FortiGate 3600C: between 1 and 32 WAD process, default 16.
FortiGate 500D: between 1 and 4 WAD process, default 2.
FortiGate 100D: between 1 and 4 WAD process, default 2.
Solution
To improve Explicit Proxy performance on FortiGate:
1) Upgrade to release 5.2 (last patch) or above.
2) Increase the number of WAD processes that can be used in parallel with the commands:
1) Upgrade to release 5.2 (last patch) or above.
2) Increase the number of WAD processes that can be used in parallel with the commands:
config globalFinding the best number of WAD workers to use for a device is not easy. The balance must be found between resources used for WAD and for other processes. It might require lots of testing with different combinations to find the correct balance.
config system global
set wad-worker-count x
end
Labels: