MySQL Configuration Tuning — Concept Check
Questions on MySQL Configuration Tuning. Key InnoDB variables: innodb_buffer_pool_size (60–80% of RAM), innodb_log_file_size, max_connections, thread_cache_size — benchmark with sysbench before and after tuning.
Questions in this quiz
8 questions on MySQL Configuration Tuning — Concept Check. Work through them here, then start the quiz to answer them and see your score.
1.Your MySQL server has 32 GB of RAM. What is the recommended range for setting innodb_buffer_pool_size?
- A10 GB to 12 GB
- B28 GB to 30 GB
- C19.2 GB to 25.6 GB
- D4 GB to 8 GB
2.A MySQL server is experiencing slow query performance. You notice that the buffer pool hit ratio is 95%. What should you do to improve performance?
- ADecrease thread_cache_size
- BIncrease max_connections
- CIncrease innodb_buffer_pool_size
- DDecrease innodb_buffer_pool_size
3.After upgrading MySQL to 8.0.30, which variable should you adjust to improve write throughput?
- Akey_buffer_size
- Binnodb_redo_log_capacity
- Cquery_cache_size
- Dinnodb_log_file_size
4.A MySQL server frequently shows 'Using temporary; Using filesort' in EXPLAIN output. What is the likely cause?
- Atmp_table_size is too small
- Binnodb_buffer_pool_size is too large
- Cinnodb_flush_method is set to O_DIRECT
- Dmax_connections is too high
5.You observe a high number of Threads_created in MySQL status. What configuration change could reduce this?
- ADecrease max_connections
- BDecrease innodb_redo_log_capacity
- CIncrease thread_cache_size
- DIncrease innodb_buffer_pool_size
6.A server with 16 GB RAM is set with innodb_buffer_pool_size = 14 GB. What is a potential issue with this configuration?
- AExcessive memory for temporary tables
- BToo many buffer pool instances
- CInsufficient memory for OS and other processes
- DInadequate redo log capacity
7.What happens if the innodb_buffer_pool_hit_ratio is consistently below 99%?
- AIncreased disk I/O
- BImproved query performance
- CReduced memory usage
- DHigher connection overhead
8.Why was query_cache removed in MySQL 8.0?
- AIt was not compatible with InnoDB
- BApplication-level caching is preferred
- CIt increased memory usage
- DIt caused excessive disk I/O