pcp
[Top] [All Lists]

Re: [pcp] Secure sockets builds have high daemon memory utilisation

To: PCP Mailing List <pcp@xxxxxxxxxxx>
Subject: Re: [pcp] Secure sockets builds have high daemon memory utilisation
From: Ken McDonell <kenj@xxxxxxxxxxxxxxxx>
Date: Sun, 15 Jun 2014 15:19:02 +1000
Delivered-to: pcp@xxxxxxxxxxx
In-reply-to: <18804700.25421398.1402627700096.JavaMail.zimbra@xxxxxxxxxx>
References: <1896810420.23212457.1402370819966.JavaMail.zimbra@xxxxxxxxxx> <5397573A.90102@xxxxxxxxxx> <1919582989.23966133.1402473837122.JavaMail.zimbra@xxxxxxxxxx> <18804700.25421398.1402627700096.JavaMail.zimbra@xxxxxxxxxx>
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.5.0
[trying again ... apologies of others are seeing this message repeated]

Just getting back into the shallow end of the pool after returning from darkest Peru ...

On 13/06/14 12:48, Nathan Scott wrote:
>
>
>> ----- Original Message -----
>> ...
> NSS init first -
> ... - avoidance on our part seems the best strategy?
>
> Secondly, the SSL session cache setup - ...
> Making our
> code not call in here at all by default seems like a good option.

The level of bloat here seems to be to be unjustified from any sort of
cost-benefit analysis I can imagine ... PCP needs to be part of solving
performance problems, not part of the problem.

Even if the additional cost is high for the uncommon (today) case of
using secure connections, we should concentrate on getting the common
case back to as close as it was before the secure socket functionality
was added.

<Prev in Thread] Current Thread [Next in Thread>