Emmanuel BILLOT wrote:
logconv.pl has more output - you might try looking at the operation times, then refer back to the access log to see what operations are taking a long timeRich Megginson a écrit :Emmanuel BILLOT wrote:Hi, Does anyones know how can we explain a 90% CPU utilization on FDS ?Many forum on the web speak about index problem or memory variables misconfiguration (|nsslapd-idlistscanlimit and co).||| |Howerver, i do not found any good web ites which explains howto | |- monitor indexes utilization| |- build/rebuilt indexes (if this is the problem)| |- configure properly FDS for having good performance| || |Our directory tree contains 15000 entries.| || |Does anyone know what can we do ? Best pratices ?|What version of FDS? What platform? What sort of hardware?The logconv.pl tool is a good place to start to diagnose indexing issues.|How to know if there is a problem on our config ?| || |Regards,| ||||------------------------------------------------------------------------ -- Fedora-directory-users mailing list Fedora-directory-users@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-directory-usersSorry i've the logconv utility, which says Unindexed Searches: 0 So i dan't explain why the CPU is so high. FDS 1.1.3 on Centos 5.1, VMWare
<<attachment: smime.p7s>>
-- Fedora-directory-users mailing list Fedora-directory-users@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-directory-users
