I am evaluating James for sending large newsletter mailings.
Others use it for that, too, and your figures don't qualify as large. :-) Barely even small. ;-)
cute. the operative phrase in that email was "test run". ;-)
Can you re-run your tests with the current v2.2 test build? There were some changes made that could significantly change the performance that you are seeing.
Nope, no big changes in performance. The run still takes about four hours. To recap:
* 4000 messages, each to a unique host. * 84 k message size * James 2.2 * 100 delivery threads * Redhat 7.3 * 1.3 GHz Pentium 3, 1.5G
What are you using for the pipeline and remote delivery spool repositories?
At the moment I'm pretty much using the default config, except the deliverythread count on the RemoteDelivery mailet is bumped up to 100 and I'm pointing at DNS that isn't on local host.
Again, any advice would be greatly appreciated!
Jeremy.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
