Assuming that the processing you're talking about is some kind of
virus scanner and/or spam scanning, that occurs under the spool/scan
directory.
Just symlink that directory to /dev/shm. In my experience that
helps disk I/O a lot.
Chris
-----Original Message-----
From: exim-users-bounces@??? [
mailto:exim-users-bounces@exim.org] On
Behalf Of Marc Perkel
Sent: Wednesday, July 02, 2008 1:57 AM
To: exim-users@???
Subject: [exim] Should queue processing be rewritten in Exim?
One thing I noticed is if you really want Exim to be super fast put the
queues in ram disk. Of course if you crash you lose everything in the
queue. One way to reduce that is to do a single try and if that try
fails hand the message off to a different server with a queue on hard
disk. But - consider this.
Suppose I'm willing to accept a few email lost in the event of a crash
and I want speed. Here's what I'd like to see.
A message comes in, is completely processed and delivered without
writing to a queue, all in ram. However if the delivery fails on the
first try then the message actually is saved to hard disk. Yes - there
is some exposure to loss of some messages on system crash, and you
accept that as a trade off for speed.
The queue is the bottleneck in the system. There must be ways to speed
it up.
Thoughts?
--
## List details at
http://lists.exim.org/mailman/listinfo/exim-users
## Exim details at
http://www.exim.org/
## Please use the Wiki with this list -
http://wiki.exim.org/
