Skip to content

Instantly share code, notes, and snippets.

@ylacancellera
Last active June 14, 2022 07:01
Show Gist options
  • Save ylacancellera/717c76ab04d1b078a80b80be1159050c to your computer and use it in GitHub Desktop.
Save ylacancellera/717c76ab04d1b078a80b80be1159050c to your computer and use it in GitHub Desktop.
## BUFFER POOL
# flush
https://fromdual.com/understanding-innodb-buffer-pool-flushing
# read-aheads
https://topic.alibabacloud.com/a/about-the-read-ahead-mechanism-for-mysql-buffer-pool_1_41_30030192.html
# AHI
https://www.percona.com/blog/2016/04/12/is-adaptive-hash-index-in-innodb-right-for-my-workload/
https://dev.mysql.com/doc/refman/5.7/en/innodb-adaptive-hash.html
## temp tables
https://www.percona.com/blog/temporary-tables-in-mysql-never-ending-story/
https://www.percona.com/blog/session-temporary-tablespaces-and-disk-space-usage
## handlers
https://fromdual.com/mysql-handler-read-status-variables
## INNODB
# stats
https://dev.mysql.com/doc/refman/8.0/en/innodb-standard-monitor.html
https://www.percona.com/blog/2006/07/17/show-innodb-status-walk-through/
# rw locks contention
https://mysqlonarm.github.io/Understanding-InnoDB-rwlock-stats/
# mutex contention
https://www.percona.com/blog/2019/12/20/contention-in-mysql-innodb-useful-info-from-the-semaphores-section/
http://dimitrik.free.fr/db_STRESS_MySQL_55_and_btr_search_latch_InnoDB_Oct2010.html
# io
https://www.percona.com/blog/2019/12/18/give-love-to-your-ssds-reduce-innodb_io_capacity_max/
https://www.percona.com/blog/2020/05/14/tuning-mysql-innodb-flushing-for-a-write-intensive-workload/
# redo logs
https://www.percona.com/blog/2008/11/21/how-to-calculate-a-good-innodb-log-file-size/
# undo logs and isolation
https://blog.jcole.us/2014/04/16/the-basics-of-the-innodb-undo-logging-and-history-system/
https://blog.jcole.us/2014/04/16/a-little-fun-with-innodb-multi-versioning/
https://www.percona.com/blog/2014/10/17/innodb-transaction-history-often-hides-dangerous-debt/
https://www.percona.com/blog/2017/05/08/chasing-a-hung-transaction-in-mysql-innodb-history-length-strikes-back/
## PRIMARY KEYS
# random pk
https://blog.jcole.us/2014/10/02/visualizing-the-impact-of-ordered-vs-random-index-insertion-in-innodb/
# varchar pk
https://www.percona.com/blog/making-aurora-write-latency-15x-higher-or-more-by-choosing-a-bad-primary-key/
# no pk
https://blog.jcole.us/2013/05/02/how-does-innodb-behave-without-a-primary-key/
## REPLICATION
# row/mixed
https://www.percona.com/blog/is-mysql-statement-based-mixed-replication-really-safe/
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment