|
On 04/25/2016 01:24 PM, ghiureai wrote:
Hello List,
I am running some search performance tests , basic ldapsearch
augument "cn" , on local ldap host with rsearch, and
seeing readwaiters: values chainng , here is a sample from dbmon
This is not from dbmon. This is from cn=monitor:
https://access.redhat.com/documentation/en-US/Red_Hat_Directory_Server/10/html/Configuration_Command_and_File_Reference/Core_Server_Configuration_Reference.html#cnmonitor
currentconnections: 41
totalconnections: 6407
currentconnectionsatmaxthreads: 0
maxthreadsperconnhits: 0
dtablesize: 8192
readwaiters: 9
opsinitiated: 41305380
opscompleted: 41305371
entriessent: 48910644
bytessent: 3952907569
currenttime: 20160425192119Z
starttime: 20160425025259Z
nbackends: 2
backendmonitordn: cn=monitor,cn=userRoot,cn=ldbm
database,cn=plugins,cn=config
backendmonitordn: cn=monitor,cn=NetscapeRoot,cn=ldbm
database,cn=plugins,cn=co
nfig
I read the documentation for dbmon output but still need to
understand what can generate this process to wait ( the search
ldap is runn locally on host), I there anything can be tune in
ldap cfg to
have this redwaiters number close to null ?
LDAP version:
389-ds-base-1.3.4.4-000.x86_64
389-ds-console-1.2.12-000.noarch
readwaiters is the number of connections that are reading a client
operation, as opposed to connections that are open but idle.
There isn't any tuning specifically for readwaiters. Why do you
think you need to do something about it?
--
389-users mailing list
389-users@xxxxxxxxxxxxxxxxxxxxxxx
http://lists.fedoraproject.org/admin/lists/389-users@xxxxxxxxxxxxxxxxxxxxxxx
|
--
389-users mailing list
389-users@xxxxxxxxxxxxxxxxxxxxxxx
http://lists.fedoraproject.org/admin/lists/389-users@xxxxxxxxxxxxxxxxxxxxxxx
