FWIW, I looked at login page timing for our site. completed in <= 10s 88% completed in <= 30s 91% (+3%) completed in <= 60s 92% (+1%) completed in <= 180s 94% (+2%)
And it slowly tails off from there; ~5-10 minutes may not be a bad number. :-) I understand the default Tomcat (in my case) session timeout is some 30 minutes (though did not verify), so a 20-25 minute 'memory savings' might not be worth twiddling the config. Something to keep in mind .... Thanks. Tom. On Jul 26, 2013, at 2:55 PM, Scott Battaglia <[email protected]> wrote: > That's up to you depending on the amount of traffic you receive and the > amount of memory allocated to the JVM heap. :-) > > It also partially comes down to how frequently you get complaints about the > issue. If 99% of your users complete the transaction in 5m or less and there > is 1% that lets it sit for an hour and then comes back, do you want to set > your session to 1.5 hours? > > On Thu, Jul 25, 2013 at 1:24 AM, Tom Poage <[email protected]> wrote: > What might be a 'reasonable' (vs. 'short' or 'long') session timeout? -- You are currently subscribed to [email protected] as: [email protected] To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-user
