Remote Delivery Performance?

[Jeremy Morony]

Hello!  I am evaluating James for sending large newsletter mailings.  I 
see on the Wiki that performance tests have been done for James handling 
incoming mail, but what about using James as an outgoing server?  Do any 
of you use James like this and, if so, what kind of performance are you 
seeing?

I am severely limited in the tests I can currently run (I can only use 
our production machine in between delivery cycles).  But based on a test 
run I did a few days ago, I'm thinking I have some configuration issues. 
 The specifics on the mailing:

* 4000 messages, each to a unique host.
* 84 k message size
* James 2.1
* 100 delivery threads
* Redhat 7.3
* 1.3 GHz Pentium 3, 1.5G memory
This mailing took about four hours, which breaks down to ten messages 
sent by each thread an hour, and never really taxed the cpu (about 20% 
cpu usage).  Yikes.  Because I'm currently limited in my testing 
capabilities, I haven't been able to go back, fiddle with it and see 
whats going on.  Do I have too many delivery threads?  (A prior test run 
with only ten threads ran much longer though).

Any comments would be greatly appreciated.  Thanks in advance.
                                                  Jeremy.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]