CPU and Ram look good….
Where is your basic fault finding data?
We run a database backend for spam control and find that cleaning up / indexing the database has dramatic effects….like after 6 months our Dell 6850 is screwed….clean it up and its disk i/o is 2% again….but this shows up under iostat….using mrtg you can see the graph climbing steadily over the months…..
A pair of SATA disks (I assume raid 1) is not very fast (on board raid?...shudder…)….also these are SATA, SATA sucks for random i/o and guess what you have a database doing random i/o……..
In terms of code, yes it is often the code at fault. Somehow developers who have written sucky code expect sys admins to spend serious time and money on hardware compensating for their bad code….it does not work.
This could be the hard thing to prove….ie….is your disk i/o inadequate or is their code so bad its causing the i/o!
If its disk i/o……
Generally, you are going to be spending most of your time reading from disk….so you need to be optimising for reads….raid5 is ideal but testing will prove this….LDAP can be distributed over disk sets…so would 4 disks in two raid1s out perform a R5 3+1? From my experience a r5 3+1 for databases is 20% faster than raid 1s….
I suspect you are very budget conscious and have no-name white boxes….so articles like this,
Can give you good pointers as what to get….generally avoid SATA, look at SAS….for databases the LSIMegaraid SAS 8888ELP in a raid 5 looks worth buying….maybe a very small disk strip is in order so small raid5 sets….
You are ahead of me at present I’m still piloting FDS….
fedora-directory-users-bounces redhat com
[mailto:fedora-directory-users-bounces redhat com] On Behalf Of Jared B. Griffith
Performance is often impacted greatly by
1) Memory on the LDAP server. Make sure you can store as much of your directory data store in RAM for fast access
2) Indexing. Make sure attributes that you search on freqently are indexed. Also, limit what fields you search on to avoid having a heavy indexing tax.
3) Make sure your network connections are stable, and your not connecting on a 100MB half duplex connection while your network equiptment is expecting a full duplex connection.
Once you have auditing those situations, please check your performance again.
50k accounts is not that much, and a 2GHz Pentium Class or 1.5GHz Core 2 system with 1GB-2GB of RAM should perform okay.
On Dec 13, 2007, at 2:36 PM, Jared B. Griffith wrote: