You might want to check the max number of file handlers for slapd.. (this is an OS setting).. under linux you use ulimit to change the maximum number of file handlers for a process. Not sure about other's. On Tue, 2004-01-27 at 16:11, Quanah Gibson-Mount wrote: > --On Tuesday, January 27, 2004 4:37 PM -0500 "Hall, Ken (IDS ECCS)" > <ken_hall@ml.com> wrote: > > > I'm running into a problem where the servers get overloaded and start > > returning "can't contact ldap server (81)", or something like it. I've > > been debating increasing the thread # from the default 32. Do you think > > this would help, or am I barking up the wrong tree? > >> > >> On 2.1, we played with the thread settings extensively. We > >> came up with a > >> standard of using 20 threads on our Solaris systems. More > >> threads than > >> that decreased performance. Our servers can handle about 55 > >> queries/second. > > Ken, > > I suggest *very* careful and consistent testing when playing with the > thread values. The performance gain you achieve by implementing threads > only goes so far, after which point, as I noted, you get worse performance. > I'm also currently investigating some behavior that I'm seeing on our > servers, where under heavy load, the simply become unavailable for periods > of time. We too are seeing the can't contact ldap server message. > > --Quanah > > > -- > Quanah Gibson-Mount > Principal Software Developer > ITSS/TSS/Computing Systems > ITSS/TSS/Infrastructure Operations > Stanford University > GnuPG Public Key: http://www.stanford.edu/~quanah/pgp.html -- Edward Rudd <eddie@omegaware.com> Website http://outoforder.cc/
Attachment:
signature.asc
Description: This is a digitally signed message part