mohit | Shared With: Everyone - Sep 24 2008 | mysql, performance, development, replication, technology, databases
There are some helpful tips in here, whether or not you use replication. In my experience, the most important thing with database performance is to minimize the time and row range over which you hold write locks -- and that's what this post is essentially about.
Quoted: Piping data through application is the best solution in many cases and is quite easy - it is trivial to write the function which will take SELECT query and the table to which store its result set and use in your application in all cases when you need this functionality.
- mohit | Shared With: Everyone - Apr 10 2008 | mysql, development, web development, replication, scalability, innovator's dilemma
Some of the referenced blog posts are quite interesting, too.
Quoted: There are interesting posts these day about future of MySQL Replication by Brian Frank and Arjen. I think it very interesting to take a look at a bit bigger picture using framework from Innovators Dilemma and Innovators Solution.
...
All these requirements made traditional databases irrelevant for many web properties - too complex and too expensive to start with. - mohit | Shared With: Everyone - Oct 12 2007 | mysql, sql, performance, databases, development, replication
You have to assume that there will be replication lag. Having said that, chopping up long queries into smaller ones (if using replication) is a good rule of thumb.
Quoted: And the final advice - do not assume very short lag time when planning your application. Having application which can adapt to lag time rather than break is very good idea. Especially it will be handy when you will be reaching replication capacity and will need to buy time to fix things, during which replication lag can be higher than normally.
- mohit | Shared With: Everyone - Feb 15 2007 | mysql, replication, data center, databases
Not rocket science, but helpful nonetheless. We used to run into minor problems until we implemented some of the techniques (primarily the session based approach) below.
Quoted: MySQL Replication is asynchronous which causes problems if you would like to use MySQL Slave as it can contain stale data.
- mohit | Shared With: Everyone - Feb 13 2007 | databases, sql server, mysql, microsoft, replication
A friend was asking me how MySQL replication compares to that in SQL Server, and I didn't know.
Quoted: Unlike MySQL one-way replication, SQL Server offers replication in a number of models: snapshot, transactional and merge.
Related Content from Around Faves
mysql
-
There are some helpful tips in here, whether or not you use replication. In my experience, the most important thing with database performance is to minimize the time and row range over which you hold write locks -- and that's what this post is essentially about.
1 FaverViewed: 6 TimesQuoted: Piping data through application is the best solution in many cases and is quite easy - it is trivial to write the function which will take SELECT query and the table to which store its result set and use in your application in all cases when you need this functionality.
- mike - May 15 20092 FaversViewed: 2 Times
- guido - Feb 22 20094 FaversViewed: 8 Times
