We had a similar problem here. Here's some details (from a note I got
from Transarc):
> The problem is that, with the advent of the extended token expiration,
> letting tokens expire slowly (say 100 hours) and because they may not
> explicitly unlog you'll quickly accumulate many rx connections which
> keeps a lot of these free entries around.
> Each new cm pag/connection uses four allocs on the rx side
> (rx_securityClass, rxkad_cprivate, rx_connection and rxkad_cconn) and it
> means, say for aix, the memory used is 428 * 4 = 1712 vs 580 real.
> Having many outstanding connections causes a big problem; with 15K
> connections we have 26M memory used instead of 8.6M of real overhead.
You can see some of this by using kdump and looking at the number of
outstanding connections, and the amount of virtual memory used. The only
way to help this is to explicitly run an "unlog" after each PAG
terminates. There is a delta in AFS 3.4 which helps cut down on this
usage, but it's still a problems unless you destroy tokens and/or
shorten the token lifetime.
Bob
--
Bob Oesterlin, IBM AS/400 Division Dept 54T, Rochester MN 55901
IBM IPNET: [EMAIL PROTECTED] Internet:[EMAIL PROTECTED]
Phone: (507)-253-4528 (tie) 553-4528 ICBMNet: 44N 92.5W
