This link has been bookmarked by 19 people . It was first bookmarked on 04 Apr 2006, by Wade Ren.
-
27 Mar 07
-
15 Nov 06
-
25 Oct 06
-
03 Aug 06
-
25 Jul 06
-
23 May 06
-
30 Apr 06
-
27 Apr 06
-
04 Apr 06
-
Thing is, while multiple MySQL threads can update multiple tables (or even multiple rows in a single table through InnoDB’s row level locking) at once, you only get a single process handling the writes of the other master. Something that’s a clear win by numbers for the local database threads over the remote replication process. And that got us in trouble. More than once.
-
Driven by reports of better performance in general and improved memory and process management in the Linux Kernel series 2.6 we upgraded all machines from 2.4.27 to 2.6.14 somewhere around mid December. Believe it or not, according to the Cacti graphs it did indeed make a difference. Not as much for the database servers, but the load on the application servers dropped significantly. Records show the system load went down from 8 to 5 in busy hours. Just by upgrading the kernel that is.
-
Tuning connection related settings in MySQL should not be necessary as your dispatchers use a single, persistent connection to your database.
-
Basically you have to cover your tracks in the peak hours while not clogging a single machine with so many processes in parallel that it crawls to a halt because of processes blocking each other at the CPU level. This is what your system load tells you.
-
-
28 Mar 06
-
21 Mar 06
-
20 Mar 06
Page Comments
Would you like to comment?
Join Diigo for a free account, or sign in if you are already a member.