overloaded. We also have a replicated slave server... every update to the main server writes through to it and it is the one that is backed up to avoid interruption service for the website.
There are certain sections of the website where all the queries are select only. So what was done was to replicate the affected tables on yet a third server. Now we're set up so that when that block of code is invoked, it connects the third db server to take the load off the main one, knowing ahead of time that there won't be any updates to it,
everyone is happy tra la la la life goes on.
My question is:
Why would they deem it necessary to use yet a third server? Could it
be because the main server and the main slave are constantly being updated and they wouldn't want to overload the main slave(which
is not on as high a horsepower of a box I know for a fact). Could it
be because maybe the subset of tables that they put on the third server
are relatively more stable and hence there arent so many writethroughs
so it can handle the complex selects better.
All theories gladly accepted...
-- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
