Is there a reason why OpenLDAP does not seem to use more than 8 cores regardless of the number of threads it is being told to use? With 16 threads it saturates 8 cores, 16 threads and 16 cores still uses 8 cores, 32 threads and 16 cores... only 8 cores are used.
On Tue, Jun 30, 2020 at 6:43 PM Quanah Gibson-Mount quanah@symas.com wrote:
--On Tuesday, June 30, 2020 10:49 PM +0000 daniel.zuniga@gmail.com wrote:
Can you offer any guidance? Thanks.
The OpenLDAP 2.4.44 release is over 4 years old.
You need to:
a) Upgrade to a current release b) Migrate off of the back-bdb/hdb backend it seems like is being used to back-mdb. They are deprecated and have serious performance issues vs back-mdb (< https://mishikal.wordpress.com/2013/05/16/openldap-a-comparison-of-back-mdb-...
).
If you are using RHEL7 or RHEL8, my company provides a free drop-in replacement:
Regards, Quanah
--
Quanah Gibson-Mount Product Architect Symas Corporation Packaged, certified, and supported LDAP solutions powered by OpenLDAP: http://www.symas.com
I assume this is with back-bdb/hdb and is because Berkeley DB does not scale beyond 8 cores.
From: Daniel Zuniga [mailto:daniel.zuniga@gmail.com] Sent: Wednesday, July 1, 2020 3:43 PM To: Quanah Gibson-Mount quanah@symas.com Cc: openldap-technical@openldap.org Subject: Re: slapd 2.4.44 Performance problems
Is there a reason why OpenLDAP does not seem to use more than 8 cores regardless of the number of threads it is being told to use? With 16 threads it saturates 8 cores, 16 threads and 16 cores still uses 8 cores, 32 threads and 16 cores... only 8 cores are used.
Thanks for the guidance. Redeploying using MDB seems to have solved the performance problem.
I have to admit, it is a little unsettling to see near-zero CPU utilization vs 100% yet the same number of requests are being supported.
We ended up sticking to the RH/CentOS7 distribution of OpenLDAP but updated to whatever their latest supported release is.
Thank you!
--On Monday, July 6, 2020 4:13 PM +0000 daniel.zuniga@gmail.com wrote:
We ended up sticking to the RH/CentOS7 distribution of OpenLDAP but updated to whatever their latest supported release is.
I strongly advise using a current release.
--Quanah
--
Quanah Gibson-Mount Product Architect Symas Corporation Packaged, certified, and supported LDAP solutions powered by OpenLDAP: http://www.symas.com
daniel.zuniga@gmail.com wrote:
Thanks for the guidance. Redeploying using MDB seems to have solved the performance problem.
I have to admit, it is a little unsettling to see near-zero CPU utilization vs 100% yet the same number of requests are being supported.
Your install of BerkeleyDB probably defaulted to using spinlock mutexes. Definitely wastes a ton of CPU, without getting anything useful done, particularly in a multi-core or multi-socket machine.
We ended up sticking to the RH/CentOS7 distribution of OpenLDAP but updated to whatever their latest supported release is.
Thank you!
openldap-technical@openldap.org
-
Daniel Zuniga -
daniel.zuniga＠gmail.com
-
Howard Chu -
Maucci, Cyrille -
Quanah Gibson-Mount