The Road Ahead...
• Work on scale-out, vs scale-up
– allow multi-terabyte DBs to be served without requiring a single giant server
So, thats what i want to know - What will be the ways to scale out, if we reach the highest limit of one single box.
I hope this time, i made it more clear.
Thanks and Regards,
Thks for replying. However, my concern is:In our production system we have 8GB of ram with 100GB hard disk. So till what limit it the Read/Write operation to LDAP goes smoothly.
Lets say - 1 row of data is 10K bytes.Please don't mind - but we are planning for the afterwards approach. (What to do - when LDAP goes slow with this configuration)
For Example - In mysql we could do first level partitioning the tables and afterwards at last resort we could do its sharding.So, my query is - Can we do anything other than upgrading H/W or OS if the I/O operation to LDAP gets slow?Thanks and Regards,Gaurav Gugnani
On Thu, Mar 15, 2012 at 12:20 AM, Quanah Gibson-Mount <email@example.com> wrote:--On Wednesday, March 14, 2012 11:08 AM +0530 Gaurav Gugnani <firstname.lastname@example.org> wrote:I'm not sure what you mean by scaling options. OpenLDAP scales, and that has been shown numerous times. How well/far it scales depends entirely on your hardware and operating system and the size of the DB in relation to those things.
First of all thks for helping me out with the issues on openLDAP.
Well today, my query is pretty generic and lot many people working on
LDAP would face such an issues.
We are using openldap 2.4.26 with BDB as backend. We've installed the
setup on linux machine of 64 bit with 4GB ram. Now, currently we have
some 10K records in it and its working perfectly fine. Our systems is
running under replication - syncrepl.
However, in near future we can foresee some million of records to turn
up. So, Can any one please advise - What are the different Scaling
options available with LDAP?
Sr. Member of Technical Staff
A Division of VMware, Inc.
Zimbra :: the leader in open source messaging and collaboration