No. of Shibboleth servers required for 6, 00, 000 users to authenticate.

[solution79]

Hello Nate / Christopher,

 

We are using SSO toolkit for authentication of users, thus can't comment on
the no. of logins per second when it comes to Shib IDP.

Is there a tool that can help to provide a dummy calculation based on no. of
users to be 6,00,000?

 

Dematri

 

From: users-bounces at shibboleth.net [mailto:users-bounces at shibboleth.net] On
Behalf Of Nate Klingenstein
Sent: Saturday, June 8, 2013 2:17 AM
To: Shib Users
Subject: Re: No. of Shibboleth servers required for 6, 00, 000 users to
authenticate.

 

What to Watch For

CPU load is primarily determined by the number of logins per second your IdP
will experience at peak load due to the cryptography of signing and
encrypting assertions.  Latency, when there is enough CPU, will be heavily
influenced by the response time of the data sources that the IdP
communicates with when authenticating users and acquiring attributes.  RAM
consumption is primarily determined by the number of concurrent login
sessions each IdP node will keep, which is itself a function of
<https://wiki.shibboleth.net/confluence/display/SHIB2/IdPStatelessClustering
> session storage and replication choices, followed by logins per second and
session duration.  Total user base size tends to be an issue for upstream
data sources to worry about and not a primary factor for load on the IdP.

CPU load is the principal bottleneck in most IdP deployments.

Please do amend if you have any changes.

 

https://wiki.shibboleth.net/confluence/display/SHIB2/IdPProdLoadTestResults 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://shibboleth.net/pipermail/users/attachments/20130611/5bec89fc/attachment.html