To avoid overloading of the modules that scan web objects for infections by viruses and other malware, requests for access to web objects are moved to a queue before being processed.
This queue is known as the anti-malware queue. When a request has been received on the appliance, it is moved to this queue by a working thread of the proxy module. It remains there until it is fetched by another thread and forwarded to a thread of one of the scanning modules.
The same applies to responses received from web servers that requests have been forwarded to.
The working threads that deliver requests and responses to the scanning modules, as well as those that are used by the modules to execute scanning activities, are referred to as anti-malware working threads or simply as AV threads.
When configuring the anti-malware queue, you can specify the following:
- Number of available anti-malware working threads
- Size of the anti-malware queue
- Maximum time for requests and responses to stay in the queue
NOTE: Moving requests and responses to the anti-malware queue is a solution to avoid load peaks occurring over a short period of time. Permanent overloading should be addressed by other measures.
Configure the anti-malware queue
You can configure settings for the anti-malware queue to avoid overloading the scanning modules.
- Select Configuration | Appliances.
- On the appliances tree, select the appliance you want to configure the anti-malware queue on and click Anti-Malware.
The settings for the anti-malware queue appear on the settings pane.
- Configure these settings as needed.
- Click Save Changes.