<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=us-ascii"><meta name=Generator content="Microsoft Word 14 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri","sans-serif";
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri","sans-serif";}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-US link=blue vlink=purple><div class=WordSection1><p class=MsoNormal>Hi,<o:p></o:p></p><p class=MsoNormal>We’re running Shibboleth SP 2.5.2 on linux host with 8 CPU and 4G RAM and I’m seeing the following behavior:<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>After startup all is fine and I see a handful of shibd threads, memory is at 165m VIRT 20m RES according to top command, CPU is negligible.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>When our QE folks run their tests, for each test they authenticate anew so I see a new session created in shibd.log<o:p></o:p></p><p class=MsoNormal>New sessions are occurring about 2-4 per second.<o:p></o:p></p><p class=MsoNormal>All goes well for a few days then they run the tests again and I see about 100+ shibd threads and VIRT and RES both go up to 3.5G and total CPU goes to about 700%, ie 7 of the 8 CPUs are pegged.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Trying to authenticate take about 10 minutes under these conditions.<o:p></o:p></p><p class=MsoNormal>Restarting shibd clears the problem and everything settles down for a few more days.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>I have session lifetime set to 3600 and timeout to 600, relayState is ss:mem<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>It seems to me that sessions (that will never be used again) are building up far faster than they expire and get cleaned out.<o:p></o:p></p><p class=MsoNormal>I’ve been looking at the docs for SessionCache and the memory StorageService but am not quite sure which values to tweak.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>I’m thinking that maybe I need to set Session timeout to something small, around 10 and reduce the SessionCache inprocTimeout to 10, cleanupInterval to 60 and then set the memory cleanupInterval to 60 as well.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Am I in the right ball park? Any ideas?<o:p></o:p></p><p class=MsoNormal>I’m also being asked “How will we handle 1000s of simultaneous logins?”<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Thanks,<o:p></o:p></p><p class=MsoNormal>Jo<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><o:p> </o:p></p></div></body></html>