A while ago, I posted the following regarding a currently large Moodle implemtnation that we are trying to 'upgade':
Well, its been months and I have learned a lot mainly through personal experience and the Moodle forums here. While we have all the physical resources to accomplish this, I am affraid we lack the technical expertise to proceed. Our team consist of myself and myself alone, and while I am willing to learn everything I need to do (i.e. corresponding technologies to enable HA, etc.) there has been something in particular I have been having some issues with. We want to use MySQL (as the company will be purhcashing an Enterprise edition of MySQL); however, I feel as if a lot of our issues as of late are all MySQL related. I have looked into a load balanced MySQL enviornment; however, the only thing that ever comes up is MySQL Cluster (which Moodle doesn't play well with to begin with). The two SQL servers we have are currently overloaded, and future plans are make one giant Moodle instance as opposed to all the individual silos we currently operate. From a DB perspective this will become one giant DB. Replication, etc. is not really my concern atm as I have succesfully configured that with hearthbeat. I am more affraid that if we are having issues with DB time outs and general performance issues with segrated DB's across multiple SQL servers, how one giant instance is going to work. Tuning will only accomplish so much...
Any tips for MySQL loadbalancing in very large implemtations?
Christopher L. Medina