Posting has been lighter than normal, as I have had the flu and it is footy finals time in Australia.
However I sat down the other day and thought about which areas I hope to cover over the next couple of months.
Given this is a blog and comments are on, if you want something covered which is not on the list feel free to add a comment with a request.
- Determine the IO/sec where the slave starts falling behind.
- Test mysqlslap running write workload on master and read workload on slave.
- Test running mysqlslap 3rd machine and connection to master and slave.
- Test running mysqlslap on replication with auto-increment column so show the effect of increment locking on master and slave.
- mysqlslap vs MySQL 5.1 row based replication
The end result is a performance report which answers the following questions:
- how many concurrent users causes the slave to fall behind
- When does network bandwidth become an issue. (test simple scp to get raw bandwidth)
- how does reading from the slave affect the slave’s ability to keep up.
- mysqlslap vs MySQL 5.1 Cluster
- running ndb Sizing script against normal database
- mysqlslap vs MySQL 5.1 Cluster Replication
- benchmarking and performance.
MySQL Toolkit and related:
- One article per mysqltoolkit tool.
- Article on using innotop
- Testing mysql partitioning, and maintenance tasks.
- How to design your database for your application (using load tables, federated storage)
- Using tmpdir as /dev/shm to help with temp table issues.
- Point in Time recovery with MySQL. Using slave (start slave until)
- Backups using LVM. => Done
- innodb_flush_method=O_DIRECT. Reason: see what the difference is, on a standalone instance and replication.
- clustering options for redundancy
- Using MySql
- using OracleXE
- using PostgreSQL
- using Hibernate