Re: maximum # of connections per dispatcher

From: <netcomrade_at_netscape.net>
Date: 5 Apr 2006 21:33:16 -0700
Message-ID: <1144297995.975326.163840@z34g2000cwc.googlegroups.com>

My dispatchers are not super-busy.

NAME     PROTOCOL                       STATUS           %TIME BUSY

OWNED
-------- ------------------------------ ---------------- ----------

---

D000 (ADDRESS=(PROTOCOL=tcp)(HOST=m WAIT 5.52262933 684
D001 (ADDRESS=(PROTOCOL=tcp)(HOST=m WAIT 5.4316637 682
D002 (ADDRESS=(PROTOCOL=tcp)(HOST=m WAIT 5.64872242 676
D003 (ADDRESS=(PROTOCOL=tcp)(HOST=m WAIT 5.41315062 681

Elapsed: 00:00:00.03

PADDR TYPE QUEUED WAIT TOTALQ AVG WAIT
---------------- ---------- ---------- ---------- ---------- ----------

00               COMMON              0   11947471  214999099 .055569865
000000010E0FD0E0 DISPATCHER          0    4749324   54667371 .086876759
000000010E0FD600 DISPATCHER          1    4671018   53634362 .087090026
000000010E0FE040 DISPATCHER          0    4780058   55772407 .085706504
000000010E0FDB20 DISPATCHER          0    4754535   54948025  .08652786

Thanks for the links. Connection pooling seems appealing, although, honestly, over the years of using MTS I've found it to be so buggy that I'd be reluctant using any more 'features' of it.

I don't fully understand how it works, it seems to be 'sharing' the socket somehow between sessions? Let's say I have 4 connections and 16 sessions enabled.. What happens if all 16 sessions want to execute something? In what wait will that result (if any).

Thanks. Received on Wed Apr 05 2006 - 23:33:16 CDT