james-server-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Danny Angus" <da...@apache.org>
Subject RE: [PATCH] Removing Scheduler dependency, refactoring service code
Date Sun, 13 Oct 2002 08:10:15 GMT
> > Using 100 delivery threads, each delivering 100 1k mails
> > to James with new connections every time Java bugs out at
> > about mail 1200, out of memory, ps shows a gazillion James
> > threads.  Re-using a single connection for each thread lets
> > 10,000 11k mails be delivered in 690 seconds on my hardware,
> > however James does freak out at this too, it stops accepting
> > connections and I don't yet know why.
> 
> FWIW, I seem to recall that there is an error where you if increase the
> threads in one place, but not in another, there isn't a good configuration
> check; it just dies.  So if you tried 100 receiving threads, that might be
> the problem.

no i didn't

 
> Assuming that you just had your regular receiving threads, then in your
> first case you had 100 threads competing to attach to each server thread,
> each one delivering a single e-mail and disconnecting.  So you'd have
> created 1200 or so connections (and handlers and other objects, 
> plus around
> 6000 scheduler entries).  In the second case, you have 100 
> delivery threads,
> but each one keeps its connection live until it is finished sending 100
> e-mails.

yes I know, that was the point..


--
To unsubscribe, e-mail:   <mailto:james-dev-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:james-dev-help@jakarta.apache.org>


Mime
View raw message