Home » Blogs » yeah's blog

Maximum Concurrent Logins

Submitted by yeah on Fri, 2009-11-06 13:17

Looks like this conversation comes up once in a while. I'm hoping we can nail down a good setting.

This setting only limits the number of users that can be logging in at any given point in time.  Default is 15 which. 

What are other schools setting this at?  We are thinking of experimenting at 50, we've heard of schools going as high as 30. 

Please let me know what you've set the Maximum Concurrent Logins to and the results you've seen.

thank you.

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

Ours is set to 15

Submitted by mcshell on Fri, 2009-11-06 15:13.

We have ours set to the default of 15 and so far have seen no need to increase the value.

Thanks,

Mike

Edison State College

Default

Submitted by rbalara on Fri, 2009-11-06 16:25.

We're also using the default. We have EAS setup to 2 AD servers (with fallaback). I set the EAS to timeout at 500ms (since it's internal). Even under heavy load, we would need over 15 users logging in less than half a second for this issue to arise. We don't have a large number of users, but that many concurrent users logging in would be very rare for us.

25

Submitted by yeah on Mon, 2009-11-09 11:23.

We whimped out and settled on 25

We're set to 15

Submitted by jtboehm on Tue, 2009-11-10 15:07.

But remember, this is per server, so if you have four servers in a PD deployment, you can handle up to 60 logins at any given time...

We're at 20

Submitted by cpalmer on Tue, 2009-12-08 13:21.

We run parallel deployment, but only one web tier up at the moment and we keep it at 20.  We found that increasing this number much above 20 actually caused many more problems under stress testing.  We're Luminis IV on Solaris boxes, so your mileage may vary.

 

All the best,

  Chris

Syndicate content