Shibboleth SP getting progressively slower

[Steve Thorpe]

Thanks Scott for your investigation & feedback.

On 1/19/12 1:09 PM, Cantor, Scott wrote:
> On 1/19/12 10:22 AM, "Steve Thorpe"<thorpe at mailbox.mcnc.org>  wrote:
>>
>> It seems likely we also encountered this bottleneck at MCNC, though it
>> wasn't with load testing per se.
>
> It is the same issue, and it does cause this problem. I do expire the
> reverse index at fault here, but the problem is it expires as a unit, and
> the expiration slides forward every time a new session shows up with the
> same NameID. This would be exactly such a case, so it never purges that
> structure and it gets slower and slower. No doubt that's what the OP is
> seeing.

Out of curiosity, what is the default duration after which the reverse 
index would expire?  If a monitoring frequency could be adjusted to be a 
bit longer, then the monitoring case presumably wouldn't encounter this 
issue even when using a fixed NameID.

Best,

Steve

-- 
Steve Thorpe
Systems Programmer/Analyst, MCNC
Email: thorpe at mcnc.org
Office: 919-248-1161
Mobile: 919-724-9654
Skype/AIM: thorpe682

Connecting North Carolina's Future Today