 |
 |
Sure, In the AJP/1.3 connector configuration for Tomcat we have: maxThreads="1000". We also increased the amount of memory available to the JVM to 8192m. In HTTPD we set MaxClients to 700. We actually run 5 Shib IDPs because we needed a seperate one for each of the Office 365 domains. The service is hosted on 2 physical machines in an active-passive failover configuration. Each host has 12 cores and 16GB of memory. All the best, Sam Jones. On Wed, Sep 18, 2013 at 12:58:17PM +0000, Andy Swiffin wrote: > Thanks Sam, that's interesting. > > Do you have some numbers of what you set things to that you could let us have? > > Cheers > Andy > > > > > -----Original Message----- > > From: Discussion list for Shibboleth developments [mailto:JISC- > > [log in to unmask]] On Behalf Of Sam Jones > > Sent: 18 September 2013 12:01 > > To: [log in to unmask] > > Subject: Re: tomcat tuning for a busy IdP > >... > > As a part of federating access to Office 365 we made a series of performance > > improvements, largely to handle the additional load generated by ECP traffic. > > > > We: > > * Upped the memory limit and thread limit for Tomcat. > > * Increased the maxclient limit for HTTPD. > > > >... > > Sam Jones. > > > The University of Dundee is a registered Scottish Charity, No: SC015096