Architecture Optimization

The following sections describe architecture optimizations.

Frequency of execution

When you program in PATROL, you will create many PSL processes, which are scheduled by the PATROL Agents scheduler. Every process will require resources. Therefore, every effort must be made to limit the number of processes and their execution schedule. This applies to all commands that will be automatically scheduled by the agent (prediscovery, discovery, collector and standard parameters)

Amount of scheduled processes

You should try to limit the number of processes you add to the agent. Although PATROL is very efficient working with vast amounts of processes, there is no need to create them if you can obtain the same functionality without them. You might be able to combine a couple of standard parameters into a single collector for example.

Amount of spawned processes

The use of global channels can reduce the number of child processes used by the KM and limit the number or redundant processes accessing the application. Also careful use of the command type facility can reduce child processes