[Date Prev][Date Next]
[Chronological]
[Thread]
[Top]
Re: Can slapd run with only one thread to operate (ITS#4842)
------=_Part_100396_21317226.1171418508303
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
What I want to do is to do operations in OpenLDAP server serially, not
concurrency
in the server. If the back database is configured to load all data in
memory, then overhead
of executing a operation is approximately equal the overhead of lock
relevant overhead in
database. So if requests are serially handled in openldap server, the lock
subsystem can
be remove from backend database.
I just want to compare difference on performance under these two strategy.
Although I use ./configure --without-threads, there are still two work
threads,(info thread in
gdb: there are two pthread_cond_wait records.)
Would you give me some suggestion to reach the goal, serially handle the
received requests
in openldap server?
Thanks a lot!
2007/2/14, Pierangelo Masarati <openldap-its@openldap.org>:
>
> Slapd by design needs at least 2 threads to work. That code is there
> exactly to
> avoid silly configurations with less than 2 threads. You're free to
> modify it,
> but then you shouldn't complain. Otherwise, if you don't want slapd to
> use
> threads you can compile it --without-threads (not --without--threads like
> you
> typed).
>
> If you could tell us what your real problem is with threads, maybe we
> wouldn't
> both waste time in this rather pointless issue.
>
> p.
>
------=_Part_100396_21317226.1171418508303
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
<div>What I want to do is to do operations in OpenLDAP server serially, not concurrency</div>
<div>in the server. If the back database is configured to load all data in memory, then overhead</div>
<div>of executing a operation is approximately equal the overhead of lock relevant overhead in </div>
<div>database. So if requests are serially handled in openldap server, the lock subsystem can</div>
<div>be remove from backend database. </div>
<div> </div>
<div>I just want to compare difference on performance under these two strategy.</div>
<div> </div>
<div>Although I use ./configure --without-threads, there are still two work threads,(info thread in</div>
<div>gdb: there are two pthread_cond_wait records.)</div>
<div> </div>
<div>Would you give me some suggestion to reach the goal, serially handle the received requests</div>
<div>in openldap server?</div>
<div> </div>
<div>Thanks a lot!</div>
<div> </div>
<div><span class="gmail_quote">2007/2/14, Pierangelo Masarati <<a href="mailto:openldap-its@openldap.org";>openldap-its@openldap.org</a>>:</span>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">Slapd by design needs at least 2 threads to work. That code is there exactly to<br>avoid silly configurations with less than 2 threads. You're free to modify it,
<br>but then you shouldn't complain. Otherwise, if you don't want slapd to use<br>threads you can compile it --without-threads (not --without--threads like you<br>typed).<br><br>If you could tell us what your real problem is with threads, maybe we wouldn't
<br>both waste time in this rather pointless issue.<br><br>p.<br></blockquote></div><br>
------=_Part_100396_21317226.1171418508303--