> -----Original Message-----
> From: Simon Byrnand [mailto:[EMAIL PROTECTED]
> A 0.5 second delay scanning a message means exactly that -
> that your email
> will arrive 0.5 seconds later. No sooner, no later. How you
> figure that you
> have to multiply that by number of users they have I have no
> idea... :)
---
That's .5 seconds of delay once I get access to a free processor
to run the filter. If the filter is processing 100,000 other email
simultaneously and each is taking .5 seconds to process, tha's 50,000
seconds, or a butt-load of time. Now if they have 100,000 CPU's each
with it's own disk, then you're right, all of those 100,000 messages
will be processed in parallel in the same .5 seconds. But if you only have
10 servers processing 50,000 seconds worth of email, that (assuming
perfect queuing and such) means it will take 5000 seconds minimimum --
best case time.
That .5 seconds isn't seconds delayed from email in to email
out, it's .5 seconds for the filter to process my 1 email. That's
why total average delay = (ave delay/email)*(#emails to process)/#CPU's.
It's easy to see with swapping overhead and queuing algorithms that
5000 seconds (~1 hour, 23 minutes total delay for each email).
You're confusing total delay with time to process 1 email. Am I
making sense yet? :-)
-l
-------------------------------------------------------
This SF.net email is sponsored by: Etnus, makers of TotalView, The best
thread debugger on the planet. Designed with thread debugging features
you've never dreamed of, try TotalView 6 free at www.etnus.com.
_______________________________________________
Spamassassin-talk mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
