Not locked into proprietary space… many options. Based from the same code tree Lib mysql vs lib drizzle – licensing gotcha libmysql gpl libdrizz bsd drizzle Maria Our delta Google patches Percona xtradb
Google patches include a better malloc And completely changed locking
Choose 5.1 or 5.4 only if you need the featuresets.
•❑ inno - row with exception •❑ myi - table -- fast in some cases and search cases ( fast inserts? without lock )•❑federated - replication not multiple master. •❑ blackhole handy for logging without inserting into db or skipping a db for fake muliple master
Much performance pain come into play with lock contention
Much performance pain come into play with lock contention Names changed to protect the innocent
Understand MTR and see if you meet that goal. tarball /dump / cpio not a valid backup
•❑ tarball /dump / cpio not a valid backup •❑ replication•❑innohot•❑lvm backup script... lvmbackup? •❑ mysqldump = 100% inno ok. single transaction .•❑xtrabackup -- free innohot
LVM and slaves give easy opportunities for creating clones for testing
Begin with having your application understand that reads and writes are different
API SHOULD KNOW THE DIFF proxy as an option if API not possible. scale writes. write own interfaces? check on it. btree index larger than memory -- writes get _slow_ Memcached – good for short lived data and caching wafflegrid -- patches to mysql -- innodb bufferpool over memcached
If you’re worried about swapping, use huge page support for mysql (linux doesn’t swap out huge pages