Optimizing MariaDB for maximum performance
3 likes2,238 views
The document outlines various strategies for optimizing MariaDB performance, highlighting the importance of examining system settings, server variables, and storage engines. It suggests specific configurations for memory allocation, connection handling, and buffers, as well as considerations for different storage engines like InnoDB and MyRocks. Additionally, it provides insights into best practices for query design and management for optimal performance.
Optimizing MariaDB for maximum performance
- 1. Optimizing MARIADB for Maximum Performance Manjot Singh Enterprise Architect MariaDB Corporation
- 4. What to Examine? System MariaDB Server Storage Engines Data and Query Design Applications and Users
- 6. Application Problems Applications and Users MariaDbDataSource vs MariaDbPoolDataSource maxPoolSize and minPoolSize COMMIT or ROLLBACK
- 8. Operating System System # sysctl -w vm.swappiness=1 # echo "vm.swappiness=1" >> /etc/sysctl.conf # echo noop > /sys/block/sda/queue/scheduler
- 9. Operating System System # cat /etc/security/limits.conf mysql soft nofile 65535 mysql hard nofile 65535 # cat /etc/fstab ... rw,noatime,nodiratime,data=writeback ...
- 10. Carefully Adjusting Flavors In Multiple Dishes MariaDB Server
- 11. Server Variables MariaDB Server max_allowed_packet = e.g. 128G-256G thread_handling = pool-of-threads thread_pool_size = # of cpu cores thread_pool_max_threads = 65536 thread_pool_min_threads = e.g. 8 thread_pool_idle_timeout = 60 max_connections = e.g. 2000-10000
- 12. Server Variables MariaDB Server query_cache_size = 0 query_cache_type = 0 skip_name_resolv = ON thread_cache_size = DON'T SET (Auto) sync_binlog = e.g. 1000
- 15. InnoDB Multipurpose Storage Storage Engines innodb_buffer_pool_size = e.g. 256M-900G ((Total RAM - (OS + Apps) - (mysqld memory + query buffers) - caches for things like binary log - other possible buffers and caches - memory tables) / 105% ) | ROUND_DOWN() ROUND(192G - ~10G - ~4G - ~1G - ~2G - ~3G) = 168G
- 16. InnoDB Multipurpose Storage Storage Engines innodb_buffer_pool_size = e.g. 256M-900G innodb_log_file_size = e.g. 2G-16G innodb_stats_on_metadata = 0 innodb_flush_log_at_trx_commit = e.g. 0? (IFLATC)
- 17. InnoDB Multipurpose Storage Storage Engines innodb_flush_method = O_DIRECT innodb_io_capacity = e.g. 2000 innodb_adaptive_hash_index_parts = e.g. 2-8 btr0sea.c
- 18. InnoDB Multipurpose Storage Storage Engines innodb_autoinc_lock_mode = e.g. 2 innodb_flush_neighbors = e.g. 0 w/SSD innodb_lru_scan_depth = e.g. 4096 innodb_sync_array_size = e.g. 16-32 (but < # of cpu cores)
- 19. InnoDB Multipurpose Storage Storage Engines innodb_read_io_threads = 4 innodb_write_io_threads = 4 History list length ROW_FORMAT=DYNAMIC OR COMPRESSED
- 21. MyRocks Writes and Compression Storage Engines rocksdb_block_cache_size = e.g. 256M-900G Rocksdb_default_cf_options = "compaction_pri=kMinOverlappingRatio; level_compaction_dynamic_level_bytes=true;" rocksdb_max_background_jobs = (# cpu cores / 4)
- 22. MyRocks Writes and Compression Storage Engines Rocksdb_default_cf_options = "block_based_table_factory= {cache_index_and_filter_blocks=1; filter_policy=bloomfilter:10:false; whole_key_filtering=1};"
- 23. MyRocks Writes and Compression Storage Engines log-bin = 1 rocksdb_flush_log_at_trx_commit = e.g. 0?
- 24. MyRocks Writes and Compression Storage Engines latin1_bin, utf8_bin, binary INDEX index_name(col1, ...) COMMENT 'family_name' rocksdb_max_open_files = -1
- 25. MyRocks Writes and Compression Storage Engines SET session sql_log_bin=0; SET session rocksdb_bulk_load_allow_unsorted=1; SET session rocksdb_bulk_load=1; SET session rocksdb_commit_in_the_middle=1; ... SET session rocksdb_bulk_load=0; SET session rocksdb_bulk_load_allow_unsorted=0;
- 27. Aria System and Temp Storage Engines aria_pagecache_buffer_size = e.g. 256M-64G aria_block_size = e.g. 2048-8096 aria_group_commit = "hard" aria_group_commit_interval = 0
- 28. Aria System and Temp Storage Engines aria_pagecache_file_hash_size = e.g. 10% open files aria_repair_threads = e.g. 4
- 29. Schema Schmema Data and Query Design SELECT col1 FROM t1 PROCEDURE ANALYSE() G
- 30. What the Query? Data and Query Design
- 31. Look it Up Data and Query Design
- 32. Place Image HereTake Another Look
- 33. THANK YOU!
- 34. Questions
- 35. THANK YOU!