Hi, Sounds like the box is asleep….if the i/o
is 2% this suggests nothing is getting to the box…..not being a LDAP expert,
but if that was a “straight” database like Oracle or MYSQL I’d think that the
problem was external to the LDAP server….if the indexing was bad, I’d expect
high disk i/o as a result/indicator…. Be interesting to see if indexing does a
thing…. regards Steven Jones From:
fedora-directory-users-bounces@xxxxxxxxxx
[mailto:fedora-directory-users-bounces@xxxxxxxxxx] On Behalf Of Jared B. Griffith Resources
are fine, and if we really need a 16 way machine this early in the game, then
we should just forgoe all of this and stick it in our regular db that sits on a
16way with 32g of mem and a fiber channel san attached to it. Hi, For applications there are lots of ways to
improve performance….with no information supplied there is no where to start… Ie, look at your disk i/o…use iostat are
the disks LDAP sits on at 100% utilisation? Even 80% is not good….if so make
bigger raid sets and/or distribute the database over differing raid controllers
and disk sets….get the utilisation down to 30%.... Is you memory full and you are into swapping?
Make sure the issue is not disk i/o bottlenecks….if not add more ram…..make
sure your swap is not exhausted….add more swap until you can get more ram… Are your switches or routers too slow?
Check their utilisation….. CPU maxed out? Where is it going? On wait?
Check disk i/o….consider dual Quad core machines…..or even 4 way quad core
machines….Dell R900s are seriously grunty boxes, have 16 cores and hold 64gig
of ram cheaply, then attach them to a SAN…. regards Steven Jones From: fedora-directory-users-bounces@xxxxxxxxxx
[mailto:fedora-directory-users-bounces@xxxxxxxxxx] On Behalf Of Jared B. Griffith I was wondering if anyone here has ever
used LDAP for a website, that will potentially have millions of LDAP accounts.
|
-- Fedora-directory-users mailing list Fedora-directory-users@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-directory-users