Hardware Requirements on Solaris SPARC 11

[Walter Forbes Hoehn (wassa)]

This does not directly answer your question, but I recently carried out a number of performance tests against a v3 IdP.  Among the questions I wanted to answer was whether or not a “high” session count adversely affected the overall performance of the IdP.  The system was configured to use JPA Storage (with postgres).  I executed an identical test plan, once against an IdP with no active sessions and once against one preloaded with 100,000 sessions.  I found no discernable difference in latency or throughput.

My testing also indicated that under normal conditions in-memory storage offered better throughput than JPA storage (duh).   Under high-load, however, the latter performed better.

Given the above, I think you might want to shift your focus from the number of sessions to the following sorts of questions:

1) How many SPs will the IdP service?

2) How often will these be accessed?

3) What will be their typical session duration?

From answers to the above, you can extrapolate what sort of throughput your IdP must handle.

-Walter


> On Mar 31, 2015, at 3:24 PM, Straubs, Christian (US - Arlington) <cstraubs at deloitte.com> wrote:
> 
> Hello everyone, 
>  
> I am currently trying to assess the following hardware requirements for running Shibboleth IdPv2 for 50,000 concurrent users.
>  
> The OS would be Solaris SPARC 11. 
>  
> Please let me know anyone’s experience/input. 
>  
> Cheers!