Home Messaging Amavisd-new filter Increase Amavis performances.

Increase Amavis performances.

Print PDF

This feature is available in Artica 1.3.073117 version

 

if your Artica server is dedicated has a mail server that handle many mails you should increase some performances values.

  • Go into Amavis configuration panel.
  • Click on Filter Behaviors icon.

  • You have 4 values on the Performances Engine area

Working directory in RAM:

By default Amavis use a folder in your disk to perform mail scanning, you can increase performance by giving a part of your RAM for scanning memory.
the minimal value is 128M
Set the field to 0 to disable this feature

amavisd child processes to spawn number:

Specifies the number of instances of amavisd child processes to spawn.
You should increase or decrease this number depending on how much memory your PC has installed.
Make sure that this number is synchronized to the smtpd maxproc setting in the postfix/master.cf file (so that you don`t end up with postfix trying to connect to a non-existant queue). For 4000 users a value between 5 and 10 would be a good starting point.
With low memory (e.g. 256 MB) a value of 2 or 3 would probably do. 

Max Requests:

Max Requests controls the approximate number of tasks each child process is willing to handle.
After that the child process terminates and the main daemon provides a new child process to take its place.
On the low side, the number should not be too small in order for the startup cost to be averaged out / sufficiently diluted over an entire child lifetime.
A value above 5 or 10 meets this goal in most amavisd-new configurations. 

Abort child if it does not complete each task in:

This value increase the timeout for the amavisd process.
The default is only 8 minutes.
When amavisd is used with other mail packages in a post queue structure, the message is transferred locally only (from the local mail queue to the amavisd loopback) and is therefore very fast.
When you use the postfix before-queue filter, the message is being transferred directly from the remote smtp through postfix to amavisd .
So for example if the remote smtp is sending a 20 megabyte message, it may take longer than 8 minutes to transmit the message (depending on network bandwidth).
Amavisd would timeout before the message had been transferred and the end user would get the following message:

Out: 451 Error: queue file write error.

Note that you may want to increase this limit even further if you see this error message from Postfix.