Allocating resources for Symantec Protection Engine
You can allocate resources for Symantec Protection Engine and limit the system resources that are devoted to scanning. You can also limit the server resources that Symantec Protection Engine uses for processing files in memory.
Symantec Protection Engine stores files in the installation directory temporary folder for scanning. You can change the location of this temporary directory to support sites with large, specialized disk configurations. The disk space that is required for this directory varies depending on the volume of data to be scanned. Symantec Protection Engine performance depends on this directory being able to accommodate a large volume of data during periods of peak use.
The file directory that you specify must already exist. Symantec Protection Engine validates the existence of the directory when you save or apply your changes.
The default temporary directories are as follows:
Linux and Solaris: <Installdir>/temp
Number of available threads for scanning
You can specify the maximum number of threads that are available for scanning.
The pool of threads that is available to Symantec Protection Engine for scanning dynamically adjusts to the load that is being processed. You can change a number of additional related parameters in the configuration file. The optimal settings for these parameters vary depending on your environment and how you use Symantec Protection Engine.
Symantec Protection Engine performance depends on the following:
Volume of data being scanned
Number of the client applications that make requests
Available memory and disk space
Number of scanning threads
If you use the RPC protocol and support multiple RPC clients, Symantec Protection Engine creates a separate pool of threads for each RPC client. (The RPC clients do not share a common pool of threads.) The number of available threads for scanning that you select for this setting is applied to each RPC client individually.
Threshold number of queued requests
Symantec Protection Engine is at maximum load when the number of queued requests exceeds the specified threshold. You can configure Symantec Protection Engine to log the event to the specified logging destinations when the queue exceeds the maximum load.
When the ICAP threshold notification feature is enabled (default value), Symantec Protection Engine takes the following actions:
Logs the event to the logging destinations
Rejects the scan request
Notifies the client that the server is too busy to process the request
When the ICAP threshold notification feature is disabled, Symantec Protection Engine continues to queue all incoming requests after the threshold is exceeded until a thread becomes available. You can configure the threshold for queued requests for Symantec Protection Engine. The client can then adjust the load balancing, which prevents the server from being overloaded with scan requests.
For logging to occur at maximum load, the logging level for the logging destination must be set to Warning or higher.
Log or send alert for maximum load every _ minutes
Symantec Protection Engine generates log entries and alerts at a prescribed interval to notify you that it is at the maximum threshold for scan requests. The alert interval is the number of minutes between each log entry or alert. The default interval is every five minutes. If you change the interval, select one that is informative but does not result in an excessive number of log entries or alerts.
You receive an SMTP alert every <n> minutes when Symantec Protection Engine rejects a scan request because it is too busy when all of the following conditions are met:
You use ICAP.
The ICAP threshold client notification feature is enabled (default setting).
You enable SMTP alerts.
You configure "Log or send alert for maximum load every __ minutes."
Symantec Protection Engine posts log entries and sends SNMP alerts for each event in which a scan request is rejected because the server is too busy.
In-memory file processing
Symantec Protection Engine can decompose and scan the contents of container files in memory, which eliminates the latency imposed by on-disk scanning. This feature can improve performance in environments in which large volumes of container and archive file formats are routinely submitted for scanning. You can limit the resources that are consumed for processing files in memory by specifying the following values:
The maximum RAM to use for the in-memory file system (in megabytes)
The maximum file size that can be stored within the in-memory file system (in megabytes)
To allocate resources for Symantec Protection Engine
In the console on the primary navigation bar, click Configuration.
In the sidebar under Views, click Resources.
In the content area under System Scanning Resources, in the Temporary directory for scanning box, type the temporary directory to be used for scanning.
To prevent scanning conflicts between Symantec Protection Engine and any other client antivirus software installed on the server, make sure that the client antivirus software avoids all scans of the Symantec Protection Engine temporary directory (for example, real-time scans, manual scans, and scheduled scans).
In the Number of available threads for scanning box, type the maximum number of scanning threads that are allowed for scanning.
The default setting is 128. The maximum recommended value is 512.
In the Threshold number of queued requests box, type the threshold number of queued requests that Symantec Protection Engine considers to be at maximum load.
The default setting is 100.
In the Log or send alert for maximum load every __ minutes box, type the alert interval in minutes.
The default setting is 5 minutes.
Under Server Resources, in the Maximum RAM used for in-memory file system box, type the maximum amount of RAM that can be used for the in-memory file system.
The default setting is 128 MB. The maximum setting is 2048 MB (2 GB).
In the Maximum file size stored within the in-memory file system box, type the maximum file size that can be stored in the in-memory file system.
The default setting is 16 MB. The maximum setting is 2048 MB (2 GB). Files that exceed the specified size are written to the disk.
On the toolbar, select one of the following:
Saves your changes.
This option lets you continue making changes in the console until you are ready to apply them.
Applies your changes.
Your changes are not implemented until you apply them. You must perform a manual restart for the changes to take effect.
Imported Document ID: HOWTO79625
Subscribing will provide email updates when this Article is updated. Login is required.