CoSign: Collaborative Single Sign-On  

cosign-discuss at
general discussion of cosign development and deployment

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: A couple of CoSign design and deployment questions

Kevin, or some one else @ UMich :)

Can you tell me the approx. number of EFTS (Effective Full-Time
Students/Staff) UMich has?



> 2. What size is your deployment at UM? Can you give me some stats, 
> like the
> hardware you are using and the number of authentications etc you 
> service a
> day. Only if this is not too much of an effort on your part, because I 
> will
> be stressing the application myself, I am just curious.

So far this month we are seeing approximately 180,000 LOGINs per day on 
a monday - thursday, as few as half that on a weekend day.  These are 
LOGIN events, of course, not unique individuals.  These 180,000 weekday 
LOGINs are associated with approximately 32,000 LOGOUT events.

We REGISTER approximately 255,000 service cookies on an average 
weekday.  120,000 of these are for  The rest are 
divided among the roughly 50 other cosign-protected services in active 
use on campus.

We're running our weblogin service on three 1u linux boxes.  Each 
machine has dual 2.8 Ghz Xeons and 4 gigs of ram.  We're using hardware 
this (relatively) "beefy" only because it was pretty much the cheapest 
thing we were willing to deploy a service on.  We have three of them so 
we can have the service physically located in multiple server rooms.  
Load average on these machines is typically around .2 (point two). :)

Copyright © 2002 - 2004 Regents of the University of Michigan :  Page last updated 15-December-2010