FortiGate configuration for conserve mode
As part of investigation by checking sample of 100 Fortigate sites from 800+ sites. The data showed that 48 Fortigate sites out of 100 sites having memory conserve mode based on crashlogs. It appears that it took a second when entering and then existing memory conserve mode. Some nodes showed multiple conserve mode instances.
Example:
29: 2026-03-09 17:47:57 green="1572 MB" msg="Kernel enters memory conserve mode"
63: 2026-03-09 17:47:58 service=kernel conserve=exit total="1918 MB" used="1541 MB" red="1687 MB"
The customer has 800+ Fortigate sites. I'd like to be sure that no impact to the customer given their large deployment. I was told that the configuration below will help to resolve the conserve mode.
Two questions are:
- Can someone help to explain what the configuration below does and how it will help? Is it the best solution to resolve or eliminate conserve mode?
- Are there any impacts and drawbacks?
#----------------------------------------------
config system global
set miglogd-children 1
set sslvpn-max-worker-count 1
set wad-worker-count 1
set scanunit-count 2
end
diag test application ipsmonitor 99
config ips global
set engine-count 2
set cp-accel-mode none
set exclude-signatures none
end
#----------------------------------------------
Thank you