Hi Sergei, > Maybe you could have a look on productivity server philosophy at > > http://www.kegel.com/c10k.html
nice read and lots of valid arguments. With the current architecture in OpenXPKI we are limited to the schemes that Net::Server offers. The preforking personality might be usable for us, but the server architecture would have to be modified somewhat to allow multiple client connection in one server process. The main reason is the global CTX object which holds many resources necessary for the daemon to work properly, including database handles etc. This can currently not easily be shared between concurring client sessions living in the same server process. The fork() call effectively isolates concurrent server processes. Addressing this issue will be a major effort which personally I'd like to address after the first release version. I agree that we should have a look at this and optimize the server process. Question: do you really face perfomance problems in your environment? In our project we are deploying OpenXPKI in a large scale environment but we don't expect high load on the server. The main reason is that the typical user will only access the server process about once a year to obtain a new certificate, which should scale nicely even with thousands of users. Cheers and have a nice weekend, Martin ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ OpenXPKI-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/openxpki-devel
