Deep Security 11 has reached end of support. Use the version selector (above) to see more recent versions of the Help Center.
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 "Aggressive" performance profile which is optimized for a dedicated manager. If the Deep Security Manager is installed on a system with other resource-intensive software it may be preferable to use the "Standard" performance profile. The performance profile can be changed by navigating to Administration > Manager Nodes. From this screen select a manager node and open the Properties window. From here the performance profile can be changed via the menu.
The performance profile also controls the number of agent- or appliance-initiated connections that the manager will accept. 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 host
If the Deep Security Manager receives a "disk full" error message from the database, it will start to write events to its own hard drive and will send an email message to all users informing them of the situation. This behavior is not configurable.
Once the disk space issue on the database has been resolved, the manager will write the locally stored data to the database.
Low disk space on the manager host
If the available disk space on the manager falls below 10%, the manager generates a Low Disk Space alert. This alert is part of the normal alert system and is configurable like any other. (For more information, see Configure alerts.)
When the manager's available disk space falls below 5 MB, the manager will send an email message to all users and the manager will shut 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 will shut down. The other manager nodes will continue operating.
