Memory Usage

[Chad La Joie]

Just to give a bit of a timeline on this.  We're preparing an IdP
release 2.3.6 with the expectation to release it in two weeks.  If
this turns out to be a valid issue (and I think it is given the
profiling information you sent me directly) it will be addressed in
that release.

On Fri, Feb 3, 2012 at 13:56, Chad La Joie <lajoie at itumi.biz> wrote:
> The other thing I'll note, in case you haven't gotten this far yet, is
> that the IdP is almost always CPU bound due to the crypto operations
> its performing.  Which is another reason I suggest performing some
> load tests sooner rather than later.
>
> On Fri, Feb 3, 2012 at 13:44, Zmuda, Matthew R <Matthew.R.Zmuda at td.com> wrote:
>> Yep I'm good with Reply cache.. and its very small.
>> I'll also triple check my code.
>> I override the SSOProfileHandler.performAuthentication... copied the code from base class and had to make some modifications, but the HttpServletHelper.bindLoginContext call is untouched and occurs at the same time/scenario as the base class.
>>
>> So in any case you should see HttpServletHelper.bindLoginContext is called two times (one by SSOProfileHandler.performAuthentication other by AuthenticationEngine.startUserAuthentication).
>>
>> Thanks!
>>
>> Matthew Zmuda | IT Solutions Developer
>> DCTS - Online Channels - Authentication and Security
>> 519-667-6052
>>
>>
>> -----Original Message-----
>> From: users-bounces at shibboleth.net [mailto:users-bounces at shibboleth.net] On Behalf Of Chad La Joie
>> Sent: Friday, February 03, 2012 1:39 PM
>> To: Shib Users
>> Subject: Re: Memory Usage
>>
>> On Fri, Feb 3, 2012 at 13:33, Zmuda, Matthew R <Matthew.R.Zmuda at td.com> wrote:
>>> Yes two login context entries are added that are almost identical. See the attached file.
>>> One by SSOProfileHandler.performAuthentication, the other by AuthenticationEngine(AuthenticationEngine).startUserAuthentication both using HttpServletHelper.bindLoginContext
>>>
>>> This is in V2.3.3 of IDP.
>>>
>>> I also see 1 ReplyCache added.
>>>
>>> When user authenticates only the second LoginContextEntry is cleared. The first one added sticks around until it expires. Same with Reply Cache.
>>
>> Well, the replay cache entry has already been discussed.  I'll look at
>> the login context entry.
>>
>>> We may at some point have a very large amount of users simultaneously using our system. So I need to fine tune this to clear our as much data as we can without affecting the integrity of the security.
>>
>> You may want to do some load testing.  There are IdP instances that do
>> many hundreds of thousands of authn's a day and at least a few that I
>> know of that do a couple million.  Not saying that your load isn't
>> higher, just saying that before you go to far trying to optimize
>> things you might want to see how the system performs out of the box.
>>
>> --
>> Chad La Joie
>> www.itumi.biz
>> trusted identities, delivered
>> --
>> To unsubscribe from this list send an email to users-unsubscribe at shibboleth.net
>>
>> NOTICE: Confidential message which may be privileged. Unauthorized use/disclosure prohibited. If received in error, please go to www.td.com/legal for instructions.
>> AVIS : Message confidentiel dont le contenu peut être privilégié. Utilisation/divulgation interdites sans permission. Si reçu par erreur, prière d'aller au www.td.com/francais/avis_juridique pour des instructions.
>> --
>> To unsubscribe from this list send an email to users-unsubscribe at shibboleth.net
>
>
>
> --
> Chad La Joie
> www.itumi.biz
> trusted identities, delivered



-- 
Chad La Joie
www.itumi.biz
trusted identities, delivered