[Date Prev][Date Next] [Chronological] [Thread] [Top]

Re: [ldap] Implementation Suggestions

> >> 1. Separate directory from account data . . . perhaps using refers of
> >> some sort to "make it look" like they're all one server/service.
> >> Directory stuff is by far the most intensely searched, updated, and
> >> involves "unusual" queries instead of a simple "give me this one
> >> entry,
> >> thanks".

Splitting up your DIT can give some performance improvements if you
have separate storage for each part.  back-meta may also give you some
flexibility options.  You may also want to review your indexing

> >>
> >> 2. Is Solaris causing too much of a bottleneck I/O wise?  It seems
> >> to  be
> >> notorious for having slower I/O than Linux, so I'm wondering if
> >> that's
> >> part of my problem.  This is Solaris 8 btw.
> >>

Solaris 9 started huge updates to the disk system and Solaris 10 keeps
it going.  (Although they were always faster than linux, in my
opinion)  Upgrading to Solaris 10 will give you a boost for free.

If you want to stick with solaris 8, there are a lot of articles out
there about tuning solaris disks with fsflushr-related settings.  Look
at docs.sun.com for solaris 8 /etc/system tunables.  Even if you
upgrade, you should look into your OS tunables for such an I/O-intense
service as ldap.

> >> 3. Maybe I have Berkeley DB configured like crap?  Thing is I
> >> can't  seem