Eugene,
Re-reading your note, it sounds like you are seeing something other than
what I initially thought. You are describing delivery time for a single
message to the list? In that case, membership list handling wouldn't be the
problem, since it only occurs once for the message. In a very busy mailing
list server, it would be more of an issue because of the large numbers of
objects, which would create work for the garbage collector.
Instead, you appear to be seeing performance in LocalDelivery related to
saving the message for each user. Although there isn't anything that we can
do in James v2 to avoid saving a copy of the message for each user, there is
a change in the v2.2.0a1 test builld that would definitely impact
performance in that area.
It would help to know precisely where James is spending its time during your
test(s).
There are some people using James for large mailing lists. Hopefully one of
them will provide some input on how they are doing that right now.
--- Noel
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
