I'd probably need more details to understand what is seen, e.g. a graph over time of
the CPU utilization of each core...
I've been discussing with people in the past who were saying "not using"
mistakingly :-)
-----Original Message-----
From: Ulrich Windl [mailto:Ulrich.Windl@rz.uni-regensburg.de]
Sent: Thursday, July 2, 2020 7:15 AM
To: daniel.zuniga(a)gmail.com; Maucci, Cyrille <cyrille.maucci(a)hpe.com>;
quanah(a)symas.com
Cc: openldap-technical(a)openldap.org
Subject: Antw: [EXT] RE: slapd 2.4.44 Performance problems
>> "Maucci, Cyrille" <cyrille.maucci(a)hpe.com>
schrieb am 01.07.2020 um
>> 18:06 in
Nachricht
<DF4PR8401MB0555595797F072395C494F66926C0(a)DF4PR8401MB0555.NAMPRD84.PROD.OUTLOOK.
OM>:
I assume this is with back-bdb/hdb and is because Berkeley DB does
not
scale beyond 8 cores.
There's a difference between "not using" and "not scaling".
From: Daniel Zuniga [mailto:daniel.zuniga@gmail.com]
Sent: Wednesday, July 1, 2020 3:43 PM
To: Quanah Gibson-Mount <quanah(a)symas.com>
Cc: openldap-technical(a)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.