Hardware Requirements on Solaris SPARC 11

[Straubs, Christian (US - Arlington)]

Walter, 

Thanks for reaching out. We are hoping for hardware specs to use in a pitch for a sub system we are attempting to implement. Specifically: 
1. CPU usage
2. RAM 
3. Disk space 

1) How many SPs will the IdP service?
	The IdP will initially not use many SPs (1-2), but in time would scale to up to 20 SPs.   
2) How often will these be accessed?
	These will be very common SPs (Google, etc.). These would be used rather frequently.
3) What will be their typical session duration?
	I would imagine anywhere from 10-30 minutes due to the nature of the SPs that would integrate. 

I know this is still vague. I am looking more for some example deployments of Shibboleth to use as benchmarks for our deployment on Solaris. 

Thank you again for your response! 

Christian Straubs 
Deloitte & Touche LLP 
Tel/Direct: (571)-814-6968 
www.deloitte.com 




This message (including any attachments) contains confidential information intended for a specific individual and purpose, and is protected by law. If you are not the intended recipient, you should delete this message and any disclosure, copying, or distribution of this message, or the taking of any action based on it, by you is strictly prohibited. 

v.E.1


-----Original Message-----
From: users-bounces at shibboleth.net [mailto:users-bounces at shibboleth.net] On Behalf Of Walter Forbes Hoehn (wassa)
Sent: Tuesday, March 31, 2015 5:55 PM
To: Shib Users
Subject: Re: Hardware Requirements on Solaris SPARC 11

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! 

-- 
To unsubscribe from this list send an email to users-unsubscribe at shibboleth.net