|
If the firewall is on conserve mode, run the following command:
get sys per status <----- It can validate whether CPU or memory is high.
After finding its memory takes more processes, run the command below to check which process is high.
diagnose sys top 2 40
After finding more, run the following command to check.
diagnose wad memory report
This output will be obtained:
******** Memory and CPU usage of wad processes ********
NAME PID STATE %CPU %MEM
wad-worker 2092 S 0.0 4.6 <------ Wad workers utilize more.
wad-config-notify 2089 S 0.0 2.7
wad-algo 2090 S 0.0 1.9
wad-manager 2037 S 0.0 1.8
wad-user-info 2083 S 0.0 1.5
wad-dev-vuln 2084 S 0.0 1.5
wad-debug 2088 S 0.0 1.4
wad-user-info-history 2087 S 0.0 1.4
wad-informer 2082 S 0.0 1.4
wad-cert-inspection 2085 S 0.0 1.4
wad-yfcs 2086 S 0.0 1.4
For a more in-depth explanation of the WAD process and how to select an individual WAD process, refer to Technical Tip: Overview of WAD process structure.
To restart the wad process and release the memory used by the wad process run 'diagnose test application wad 99'
For other methods on how to restart the WAD process, refer to Technical Tip: How to restart the WAD process.
Related article:
Technical Tip: Reduce memory usage by reducing the number of spawned daemons
|
