Tmpfs for amavisd-new

Revision as of 19:20, 5 August 2011 by Irfan (talk | contribs) (Created page with "{{WIP}} __TOC__ This document gathers requirement and steps required to configure amavisd to use a ramdisk for its temporary data processing. The steps are specific to RHEL serv...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

This document gathers requirement and steps required to configure amavisd to use a ramdisk for its temporary data processing. The steps are specific to RHEL servers running Zimbra 6.x or higher.

Note

This is not a Zimbra feature. I've documented the steps here just for reference who require amavisd with tmpfs. Please check Bug 13607 [1] and Bug 8081 [2] for more details.

Requirement

Amavisd-new's speed may be limited by the speed and latency of your disk I/O, which can causes huge active mail queue, with a very limited delivery rate. Moving amavisd tmp directory to ramdisk will eliminate disk read/write operations. It can make a lot of difference in amavisd mail processing speed.

Pre-requisites

1. You need a kernel that is capable of creating and using a tmpfs filesystem 2.

Sizing

If you run n amavisd-new instances and each one accepts mails of $message_size_limit, then you need a tmpfs of size will be.

n * (1 + max(expansionfactor)) * $message_size_limit

Steps

/etc/fstab /dev/shm /var/amavis tmpfs defaults,noexec,nodev,nosuid,size=150m,mode=750,uid=7509,gid=54322 0 0

Stop amavisd-new mount /var/amavis Start amavisd-new

Jump to: navigation, search