Have you double checked the hardware? Are you using 5400rpm drives, or 15k rpm drives? I/O bottlenecks are common, if you can't read the data fast enough, then it will definitely be slower, and appear to have more issues that it really does. If the client can't/won't change/alter the code, then maybe looking at changing the hardware would be better. Having a smaller drive size raid array with faster harddrives may solve the I/O bottleneck if that is the case.
And maybe it is just poorly written queries with crappy indexing? Maybe look at the slow query log, and ensure that the RIGHT indexes are there (140gb/21gb index doesn't mean that the indexes are the correct ones) Going to a replication setup may not be the solution to your problems, and could just be a bandaid (and prolly cause you many sleepless nights maintaining data integrity). Find out the cause of the problem, before adding to it. Steven Staples > -----Original Message----- > From: Nunzio Daveri [mailto:nunziodav...@yahoo.com] > Sent: August 4, 2010 2:40 PM > To: mysql@lists.mysql.com > Subject: Moving from one MySQL server to three MySQL servers? > > Hello Gurus :-) I was running a simple load generator against our 16GB > Dual > Quad core server and it pretty much came down to it's knees within two > hours of > running tests. The customer DOES NOT WANT to change any code, they just > want to > throw hardware at it since it took them a year to create all of the code. > It is > a 140GB database with 21GB of indexs all using InnoDB - currently doing 70% > reads and 30% writes. > > My question is what is the best way of distributing the load without > changing > any of the php / perl code that their web server uses? This is what I am > thinking but need someone to tell me it is a good idea or bad please? > > 1. Setup a single master and 2 slaves. The question is how to tell the web > servers to get all the read data from the slaves and to only write to the > master? > > 2. Install a MySQL proxy box and let mysql proxy handle the load, problem > is now > it is the SPOF! > > 3. Use DNS round robin, BUT how to tell round robin to ONLY go to master > for > writes and ONLY use one of the 2 slaves for reads? > > Any links, ideas or suggestions is most appreciated. > > TIA... > > Nunzio > > > > No virus found in this incoming message. > Checked by AVG - www.avg.com > Version: 9.0.851 / Virus Database: 271.1.1/3023 - Release Date: 08/04/10 > 00:45:00 -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/mysql?unsub=arch...@jab.org
