
database
Fonction stockée mysql | Réflexe
cassandra
Replication enables data from one MySQL server, called the master, to be replicated to one or more MySQL servers, called slaves. Replication is mostly used as a scale-out solution. With scale-out solution we are basically spreading the load among multiple slaves to improve performance. In this solution, all writes and updates take place on the master server, while reads take place on one or more slaves. This model improves both the write performance as well as the read performance across an increasing number of slaves. This scale-out solution that I have discussed above is actually master-slave replication, and this is the kind of replication that we will be setting up today.
Setting up Master-Slave Replication with MySQL | ovais.tariq
Using O_DIRECT on Linux and INNODB to Fix Swap Insanity « Kevin Burton’s NEW FeedBlog
November 3, 2007 By Peter Zaitsev 39 Comments My last post about Innodb Performance Optimization got a lot of comments choosing proper innodb_buffer_pool_size and indeed I oversimplified things a bit too much, so let me write a bit better description. Innodb Buffer Pool is by far the most important option for Innodb Performance and it must be set correctly. I’ve seen a lot of clients which came through extreme sufferings leaving it at default value (8M). So if you have dedicated MySQL Box and you’re only using Innodb tables you will want to give all memory you do not need for other needs for Innodb Buffer Pool. This of course assumes your database is large so you need large buffer pool, if not – setting buffer pool a bit larger than your database size will be enough.

