Deep Security Manager performance features

Performance profiles

Deep Security Manager uses an optimized concurrent job scheduler that considers the impacts of each job on CPU, database and agents or appliances. By default, new installations use the Higher Capacity performance profile optimized for a dedicated manager. If Deep Security Manager is installed on a system with other resource-intensive software, it might be preferable to use the Standard performance profile. To modify the performance profile, navigate to Administration > Manager Nodes, select a manager node, open Properties, and then use the menu to make changes.

The performance profile also controls the number of agent- or appliance-initiated connections that the manager accepts. The default of each of the performance profiles effectively balances the amount of accepted, delayed, and rejected heartbeats.

Low disk space alerts

Low disk space on the database

If Deep Security Manager receives a Disk Full error message from the database, it starts to write events to its own hard drive and sends an email message to all users informing them of the situation. This behavior is not configurable.

If you are running multiple manager nodes, the events are written to the disk of whichever node is handling the event. For more information on running multiple nodes, see Install Deep Security Manager on multiple nodes.

Once the disk space issue on the database has been resolved, the manager writes the locally stored data to the database.

Low disk space on the manager

If the available disk space on the computer where Deep Security Manager is installed falls below 10%, the manager generates a Low Disk Space alert. This alert is part of the regular alert system and is configurable. For more information, see Configure alerts.

If you are running multiple manager nodes, the node is identified in the alert.

When the manager's available disk space falls below 5 MB, the manager sends an email message to all users and the manager shuts down. The manager cannot be restarted until the available disk space is greater than 5 MB.

You must restart the manager manually.

If you are running multiple nodes, only the node that has run out of disk space is shut down. The other manager nodes continue operating.