Re: nslcd threads and connections: 5 too many?

[Chris Hiestand <chiestand [at] salk.edu>]

On Mar 10, 2012, at 11:33 AM, Arthur de Jong wrote:

> The number was chosen rather arbitrarily early during development. With
> nss_ldap there were about 5 connections open from an average system (I
> think) so that would not be an increase. nscd also has 5 thread by
> default.

Ah, that explains it, thanks for the context.

> There have not been detailed studies on the ideal number of threads but
> I expect that even two threads would be sufficient for most cases. I
> would avoid using just one thread because an application could be
> performing two requests simultaneous (e.g. go over all users and find
> groups per user).

I'm going to reduce my less busy clients to 3 threads then.


> If anyone can provide good reasoning why another number should be the
> default (preferably supported by some facts) I can change the default.

If 2 or 3 is sufficient for 90%+ of the installations out there it might
make sense to decrease the default. 

On the other hand, heavy users like me should know enough to configure their
installation to their needs. In support of that, perhaps the nslcd.conf(5)
man page should be updated to mention there is one connection to the ldap
server per thread (diff attached).

Attachment: nslcd.conf.5.xml.diff
Description: Binary data

If I can provide any better data later I'll send it in.

Thanks,
Chris

Attachment: smime.p7s
Description: S/MIME cryptographic signature

-- 
To unsubscribe send an email to
nss-pam-ldapd-users-unsubscribe@lists.arthurdejong.org or see
http://lists.arthurdejong.org/nss-pam-ldapd-users/