james-server-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Serge Knystautas" <ser...@lokitech.com>
Subject Re: Spool processing (was 'Spool manager on M$ SQL' at James-User)
Date Thu, 14 Mar 2002 13:00:00 GMT
Have you tried boosting the number of connections the pool has?  Someone
spotted that the default was 2 and you can set a <max> parameter to the pool
to something higher.  This might get you much better throughput.

The spool manager configuration shouldn't affect incoming throughput.  The
SMTP Handler will grab a db connection and puts a message in the top of the
spool, and separately the spool manager grabs and processes it.

Maybe what you could do is define 2 db pools, have the SMTP manager use one
that has a higher connection limit, and the spool manager use a similarly
configured but different pool with relatively few connections.

I don't know... the problem is these two thread groups (SMTP handler and
spool manager) are fighting over connections in the db pool, and I don't
know any pooling code that supports prioritization of requests for db
connections.

Serge Knystautas
Loki Technologies - Unstoppable Websites
http://www.lokitech.com/
----- Original Message -----
From: "David Shpil" <david@harmeron.com>
To: "James Developers List" <james-dev@jakarta.apache.org>
Sent: Thursday, March 14, 2002 5:16 AM
Subject: Spool processing (was 'Spool manager on M$ SQL' at James-User)


> Guys,
>
> I'm still trying to get spool manager working better under some load.
> As I mentioned before, message rate of more then 4 per sec overloads
> the spool manager and dramaticly increases local delivery time. If the
> message rate remains the same for some time, a local delivery time
> continues to grow.
>
> IMHO, the problem is that Spool Manager grabs all messages available from
> the spool and then processes them. In my case, message rate is relatively
> high
> and it causes the manager to grab more and more messages every time.
>
> So, first thing I would like to achieve is to provide kind of "quality of
> service"
> for local delivery. In other words: I want to have minimal "local delivery
> message rate",
> regardless of "incoming message rate". This might be done by making a
spool
> manager
> to grab limited number of messages ...
>
> Am I going in right direction? If I am, what changes should be done at
> sqlResouces.xml file?
>
> TIA
>
> David.


--
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