I can reproducably, impact on FDS performance by running:
$ getent passwd | cut -d: -f 1 | while read i; do id $i; done
Since you can reproduce the syndrome at will, and in a steady state,
just run that command above and then go run 'pstack <fds_pid>' on the
server machine.
That'll dump the thread stacks and tell you where the server is spending
its time
(assuming, which I am, that we've already established that the server is
for some reason burning CPU when subjected to this load).
--
Fedora-directory-users mailing list
Fedora-directory-users@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/fedora-directory-users
