> We were testing James2.2.0.8.a on our servers to handle a large number of
> incoming and outgoing messages. The test conditions were
> 4. Repository used � Default file Repository
> We figured out some details that concerned us.
> 1. We tested james for around 8000 messages/min and noticed that it had
the
> CPU usage up to 90-99% . In this test we are sending and receiving
messages.
> There was increase of memory at the rate of 8M/min
Remember that James is capable of spooling incoming messages faster than it
can finish processing them.
My guess, a priori, is that the increase is related to the growing backlog
in the spool system. The file repository keeps its index in-memory. At
8000 messages per minute, I suspect that the spool was growing rapidly,
meaning that the in-memory indices are also growing rapidly. In such
situations, the JDBC spool is better, especially if you tune the maximum
query size. The resource utilization is much more controlled and bounded.
At some point, we need to enhance James to provide feedback to the SMTP
Handler that the system is full, and resources are needed to process the
spool.
> 2. When we reduced it to 400 message/min and James used around 5% of CPU
> time, and the rate of memory increase was 1M/min. In this specific test we
> had the Match set to �All� and the Mailet was set to �Null� and we were
just
> receiving messages.
Although I have not run it on the most recent test builds, when I run that
exact test, I do not see any memory increase beyond the point where James
has setup the steady-state resources it needs to process that message rate.
--- Noel
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
