'idp.service.metadata.checkInterval' on specific time
Cantor, Scott
cantor.2 at osu.edu
Mon Mar 18 09:24:30 EDT 2019
On 3/18/19, 9:05 AM, "users on behalf of Zico" <users-bounces at shibboleth.net on behalf of mailzico at gmail.com> wrote:
> Sorry.. 'drastic under-resourcing' means?
A couple of gigs of heap and maybe 4G of RAM is enough to run a high volume IdP if you had to.
> Generally these servers are running with 16GB physical memory; allocated max 6.5G for shibboleth only...
That's far more than necessary and you clearly have some other problem. Perhaps you're giving it too much memory and causing GC issues. I handle 250,000+ logins a day with 2.5G on a 16GB machine, and there are zero issues with metadata reload of the InCommon aggregate.
-- Scott
More information about the users
mailing list