[Date Prev][Date Next]
[Chronological]
[Thread]
[Top]
Re: limiting the number of running slapd's
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Sat, 13 Apr 2002, David Wright told this:
>> This evening whilst checking so stuff, I noticed that there were over 30
>> occasions of slapd running, this is more than likely a couple of days
>> useage. How do I stop this.
>
> Did you notice that they all had EXACTLY the same VSZ and RSS? That's
> because they aren't actually distinct processes, but threads of a
> single slapd process. That means, among other things, that slapd isn't
> really using the sum total of all those memory allocations. (Since
> thread support has sort of been welded onto Linux as an afterthought,
> a lot of tools don't really support the distinction between threads
> and processes.)
I had not and have never really looked at this side of Linux before :) I
was not worried by memory useage as there is virtually none in the first
place, it was just the number of incidents.
> A multithreaded slapd by default maxes out at 32 threads (you will
> find a few more, because the few threads which aren't used to handle
> requests don't get counted toward that total). On a site with a heavy
> ldap querry load, you'll actually want to increase that number (using
> the threads directive in slapd.conf). On a site with a very small ldap
> querry load, you can get away with decreasing it, but I don't really
> see any advantage in doing so, because they won't be heavily taxing
> your CPU and memory anyway.
LDAP is used mainly by my mail pc to verify local users as 99% of them
don't exist on every box on my network. loading is not really an issue
for me as Exim, Courier Imap and others all refer to the ldap server,
just need tp sort out aliases now :)
Sean
- --
Sean Rima http://www.tcob1.net
Linux User: 231986 Jabber: tcobone@jabber.org
THE VIEWS EXPRESSED HERE ARE NOT NECESSARILY THOSE OF MY WIFE.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: Use GPG for Secure Mail
iEYEARECAAYFAjy5RFYACgkQeR/L2ZZp3E+M0wCg58GYUgweYqpULC45USB0d+bL
LO4An1i0+FXdv844BRXip+hs8XRREtqk
=K/QS
-----END PGP SIGNATURE-----