directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Emmanuel Lecharny (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DIRSERVER-2233) Apacheds sometimes slow query
Date Fri, 13 Jul 2018 09:02:00 GMT

    [ https://issues.apache.org/jira/browse/DIRSERVER-2233?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16542739#comment-16542739
] 

Emmanuel Lecharny commented on DIRSERVER-2233:
----------------------------------------------

Hi,

we would need your complete configuration (as a LDIF file) and also the exact requests that
take time.

Thanks !

> Apacheds sometimes slow query
> -----------------------------
>
>                 Key: DIRSERVER-2233
>                 URL: https://issues.apache.org/jira/browse/DIRSERVER-2233
>             Project: Directory ApacheDS
>          Issue Type: Bug
>          Components: ldap
>    Affects Versions: 2.0.0-M20
>         Environment: We installed the apacheds-2.0.0-M20 in redhat 6.7,and now more than
10 thousands entries stored in it,
>            Reporter: cokuehuang
>            Priority: Major
>              Labels: performance
>   Original Estimate: 96h
>  Remaining Estimate: 96h
>
> Could you give me some advise that how to improve apachds query performance when more
and more entries created in apacheds, and I have a doubt that how many entries apacheds can
support? The apacheds always works well until one day it became query slow sometimes, total
numbers of entries in apacheds become bigger and bigger ,now we have almost 8000+ entries
in "ou=A" and 3500+ entires in "ou=B".Under normal circumstances, it costs only serveral
ms when query some entries, but sometimes it will costs hundreds or even tthousands ms,we
found that when it query slow ,the cpu of apacheds' process is higher.
> Most of query fitler is like this: "objectClass=CustomPerson" or "someAttributeType=*"
> we do something to solve the problem of slow query:
> 1.add index of entry property and set a big cash size(10000 or more)
> 2.Increase the CashSize of partion from 10000 to 20000,as we think the total entries
in server is above 10000(3500+8000+other entries in our server).
> 3.there are many attributes in ou=index , most Cash size is 100, and we don't know whether
increase their size can improve the speed of query when entrie become more and more
> Looking forward to your reply!



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message