[Date Prev][Date Next]
[Chronological]
[Thread]
[Top]
[Solved] Poor performance on Solaris
- To: <openldap-technical@openldap.org>
- Subject: [Solved] Poor performance on Solaris
- From: <Juergen.Sprenger@swisscom.com>
- Date: Mon, 7 Mar 2011 13:57:58 +0100
- Accept-language: en-US, de-CH
- Acceptlanguage: en-US, de-CH
- Content-language: en-US
- Thread-index: Acvcx0iXgM7pYjDzQrOeU6ofoWozuw==
- Thread-topic: [Solved] Poor performance on Solaris
Hi,
first I wish to thank all those who supplied helpful hints to solve the problem, especially Quanah Gibson-Mount and Howard Chu.
My performance issue was solved by switching from memory mapped keys to shared memory keys for hdb as suggested by Quanah and Howard.
Putting 'shm_key 10' into slapd.conf and restart of slapd solved the problem.
Performance improvement was about factor 10 on the Solaris box.
As the problem was gone connection logging was switched off, which additionally doubled throughput as Solaris sylog can't do asynchronous logging.
During further tests slapd stopped responding when many concurrent connections were active.
This behaviour was caused by default settings in /etc/system.
Adding two lines to /etc/system and reboot solved the problem:
set rlim_fd_max = 16368
set rlim_fd_cur = 8192
Should be enough for about 8000 connections.
Performance before:
box1:
hardware: Sun Microsystems sun4v SPARC Enterprise T5120
memory:32 GB RAM
os: Solaris 10 s10s_u9wos_14a
searches (avg/second): 1521
Performance after:
box1:
hardware: Sun Microsystems sun4v SPARC Enterprise T5120
memory:32 GB RAM
os: Solaris 10 s10s_u9wos_14a
searches (avg/second): 37000
My next step will be tuning network parameters.
Juergen Sprenger