CoSign: Collaborative Single Sign-On  

cosign-discuss at
general discussion of cosign development and deployment

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]


Hi all,

as from my previous messages, I have been doing a number of load tests
on our cosign install.

I have been noticing an alarmingly high amount of time the application
(the cosign daemon) spends in the system. It can by up to 3 times the
user time.

I am sure it is no the fork, because i have hacked at the daemon to
prefork a large number of children and handle the connections like that.

When I do an strace of one of the daemons it give nothing which stands
out, except for the incredibly large number of getpid calls. I am to
understand this is the SSL Cyrpto multi-threaded support. I have gotten
ride of a lot of this because defining callbacks for these, and yet
still a high amount of system time is spent.

Anyone seen this, or got any ideas?

Copyright © 2002 - 2004 Regents of the University of Michigan :  Page last updated 15-December-2010