shibd Memory Usage

Andy Bennett andyjpb at
Fri Sep 26 12:38:14 EDT 2014


>> Oh yes, I see. We're not seeing much concurrency because we only access
>> the FastCGIs during an actual Shibboleth Login event rather than on
>> every page load. Indeed, we've only got one of each of the authorizer
>> and responder actually running at the moment so I'd imagine that would
>> limit the number of threads in shibd to around 2?
> I don't know how FastCGI works exactly, I thought there was still a pool
> of processes running each type of binary. There certainly is with Apache's
> FCGI implementation.

That's about right. In our case we have a pool of 1 for each type of
Shibboleth Fast CGI: authorizer and responder.


andyjpb at

More information about the users mailing list