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

Re: Possible bug?



This is likely just BerkeleyDB spinlocking.  It's generally viewed
as feature, not a bug.  The fact that it causes load is inherit.

If you don't like BerkeleyDB spinlocking, you can may be able
to disable it (see their configuration documentation) or use
an alternative DBM (such as GDBM).

Kurt

At 10:35 PM 7/11/00 -0400, William Yodlowsky wrote:
>I didn't want to use ITS because I'm not sure if this is really a bug or
>not...
>
>I'm using OpenLDAP 1.2.11 + db2 + libwrap with nss_ldap on SPARC Solaris
>7.
>
>During queries, slapd seems to spike rather high in terms of CPU usage
>(like sometimes 90%...).  To get an idea of what's going on, I did a
>truss(1) on slapd while it was queried and saw it (apparently) spin like:
>
>yield()                                         = 0
>time()                                          = 963368437
>yield()                                         = 0
>time()                                          = 963368437
>yield()                                         = 0
>time()                                          = 963368437
>yield()                                         = 0
>time()                                          = 963368437
>yield()                                         = 0
>time()                                          = 963368437
>yield()                                         = 0
>time()                                          = 963368437
>yield()                                         = 0
>time()                                          = 963368437
>
>ad nauseam.  It does this literally tens of thousands of times and appears
>to drive the CPU way up.
>
>I'm not a programmer by trade, but this doesn't appear normal... should I
>be checking something config-wise or start an Issue?
>
>Thanks for the great, free software.
>
>`-
>William Yodlowsky
><wyodlows@nj.devry.edu>