User login
Navigation
Active forum topics
Recent comments
- Load balance lp5
13 hours 46 min ago - can I force two users to have the same email address
15 hours 31 min ago - Channel ID
20 hours 4 min ago - Thanks Todd I will start
21 hours 6 min ago - Something in LDAP
1 day 14 hours ago - Glad you solved it
1 day 15 hours ago - I'm not sure if my reply went
1 day 16 hours ago - GCF redirect URL
1 day 16 hours ago - Owner
1 day 18 hours ago - browser title bar revisited
1 day 22 hours ago
Who's new
- jojobb
- nishimei
- Raul123
- leggn
- srattans
Who's online
There are currently 2 users and 8 guests online.
Online users
- ejames
- libdms
Recent blog posts
- Sun One Communications Suite 5
- Job Opportunity for Luminis Portal Developer - Suffolk County Community College
- Security Warning when using MS IE?
- Intermittently asking for ID and PIN
- Job Opportunity - Lehigh University - Senior Analyst, Library and Technology Services
- Blackboard 9 GCF Connector Problem
- Luminis Portlet Development PreConference session needs more signups
- Critical Vulnerabilities on TomCat/Apache web servers?
- so long, and thanks for all the fish
- SAML for Concur
Poll
What does your school use for student email?
In house Microsoft Exchange
15%
In house Sun JCS
12%
In house Zimbra
5%
In house Other
6%
Hosted Microsoft Live@EDU / Office365
21%
Hosted Google Apps for Education
39%
Hosted Zimbra
1%
Hosted Other
2%
Total votes: 111
- Login or register to post comments
- Older polls

lmb event rate
I'm guessing that most schools use the default settings.
For larger schools, like mine (30,000+ students), we've increased the rate to handle the large event floods at registration times.
PollingInterval = 20;
MaxResultSizePerPoll = 300;
Depending on your hardware, throttling the LMG may be necessary if your LDAP or database are performing poorly when large numbers of events are being processed.
lmb event rate
We use:
PollingInterval = 10;
MaxResultSizePerPoll = 20;
which comes out to 120/minute. This was intentionally rate limited to allow our complex Active Directory/eDirectory adaptor time to process. We kept the interval short (10 seconds) to ensure that there was very little lag from the time the user applied and was accepted to the time when the portal account was available so that they could register.
I am not sure we keep up during heavy reg periods (like now), but we never get very far behind.