From: "Michel Vaillancourt" <[EMAIL PROTECTED]>

<<jdow's plugged nickel's worth>>Based on the bad case I ran his
machine should do on the order of 10 to 30 seconds per email depending
on the speed of his processor. At 30 seconds per that gives him the
capacity, with delays to be sure, for 3000 emails per day. When they
come in batched there will be several minutes of delay. But for most
people's needs for a single user 3000 emails is somewhat more than is
to be expected.

{^_-}   Joanne, who has a bad habit if running numbers. And I note he
        might be able to run two instances to get SOME benefit from
        paralleling the DNS lookups.


ext1:~# cat /proc/cpuinfo
[..trim..]
model name      : Pentium II (Deschutes)
stepping        : 2
cpu MHz         : 398.982
cache size      : 512 KB
[..trim..]

ext1:~# free -m
            total       used       free     shared    buffers     cached
Mem:           251        247          4          0         16         12
-/+ buffers/cache:        217         33
Swap:          760        118        642

ext1:~/pflogsumm-1.1.0# sh yesterday.stats.sh  | head -n 10
Postfix log summaries for Aug  8

Grand Totals
------------
messages

  9867   received
  9955   delivered

ext1:~# grep -i spamd /var/log/mail.log | grep -i identified | head
Aug  9 06:42:43 ext1 spamd[465]: spamd: identified spam (17.9/5.0) for
nobody:8 in 1.3 seconds, 1390 bytes.
Aug  9 06:43:04 ext1 spamd[466]: spamd: identified spam (24.6/5.0) for
nobody:8 in 1.4 seconds, 26292 bytes.
Aug  9 06:43:39 ext1 spamd[466]: spamd: identified spam (44.9/5.0) for
nobody:8 in 1.6 seconds, 2637 bytes.
Aug  9 06:46:55 ext1 spamd[466]: spamd: identified spam (14.7/5.0) for
nobody:8 in 1.3 seconds, 1415 bytes.
Aug  9 06:52:00 ext1 spamd[466]: spamd: identified spam (23.0/5.0) for
nobody:8 in 1.2 seconds, 2692 bytes.
Aug  9 06:58:33 ext1 spamd[466]: spamd: identified spam (16.6/5.0) for
nobody:8 in 1.4 seconds, 1313 bytes.
Aug  9 07:07:06 ext1 spamd[466]: spamd: identified spam (15.6/5.0) for
nobody:8 in 2.8 seconds, 21911 bytes.
Aug  9 07:07:42 ext1 spamd[466]: spamd: identified spam (12.7/5.0) for
nobody:8 in 7.1 seconds, 12636 bytes.
Aug  9 07:11:10 ext1 spamd[466]: spamd: identified spam (51.2/5.0) for
nobody:8 in 1.6 seconds, 3174 bytes.
Aug  9 07:11:54 ext1 spamd[466]: spamd: identified spam (42.1/5.0) for
nobody:8 in 3.9 seconds, 2034 bytes.

... and I'm running 66 optional tests above and beyond the "stock" set that
come with SA, so that makes 85 rules tests my machine is running through.
Its running Postfix, Spam Assassin, ClamAV, Courier IMAPD/POPD with a local
replica of MySQL for authentication.  I'm running six spamc clients
concurrently on the machine to keep delays down.

I don't know if that data-point is of use in the discussion, but there it
is.

And it appears you do run into swap space.

Note that I run a rather unconservative 40+ SARE rule sets. That slows
down scanning materially. It also runs up the typical spamd size to the
60 megabyte range. If I ran that few tests I could probably clear each
message in a fraction of a second. (I've no idea how many tests I run.
If I had to hazard a guess I'd say well over 1000 and (slightly)
possibly as many as 2000. On that poor old overstressed 66 MHz machine
I was taking 20 to 30 seconds per message and was running as few as
1/4th the number of rules.)

{^_^}   I have enough machine for the needs so I throw it at the spam
       solution. {^_-}

Reply via email to