Server configuration tuning in MySQL - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is the purpose of server configuration tuning in MySQL?

Server configuration tuning adjusts MySQL settings to improve performance, resource use, and stability based on the workload and hardware.

beginner

Which MySQL variable controls the maximum number of simultaneous client connections?

The max_connections variable sets the maximum number of clients that can connect to the MySQL server at the same time.

intermediate

How does the innodb_buffer_pool_size affect MySQL performance?

It sets the amount of memory InnoDB uses to cache data and indexes, reducing disk reads and speeding up queries.

intermediate

Why is it important to tune the query_cache_size carefully?

A too-large query cache can cause overhead and slow down writes, while a properly sized cache speeds up repeated SELECT queries.

beginner

What tool can you use to check the current MySQL server status and variables for tuning?

You can use the SHOW STATUS and SHOW VARIABLES commands to view server performance and configuration details.

Which MySQL variable controls the size of the InnoDB buffer pool?

A thread_cache_size

B max_connections

C query_cache_size

D innodb_buffer_pool_size

The innodb_buffer_pool_size variable sets the memory size for caching InnoDB data and indexes.

What happens if max_connections is set too low?

A Clients may be refused connections when too many try to connect.

B The server will use too much memory.

C Queries will run slower.

D Disk space will fill up quickly.

If max_connections is too low, new clients cannot connect once the limit is reached.

Which command shows the current MySQL server variables?

A SHOW STATUS;

B SHOW VARIABLES;

C SHOW TABLES;

D SHOW PROCESSLIST;

SHOW VARIABLES displays the current configuration settings of the MySQL server.

Why should you avoid setting query_cache_size too large?

A It disables caching completely.

B It will cause the server to crash.

C It can cause overhead and slow down write operations.

D It increases disk usage.

A large query cache can slow down writes because it must invalidate cached queries.

Which MySQL variable affects the number of threads cached for reuse?

A thread_cache_size

B max_connections

C innodb_buffer_pool_size

D query_cache_size

thread_cache_size controls how many threads MySQL keeps ready to reuse, improving connection speed.

Explain how tuning innodb_buffer_pool_size can improve MySQL performance.

Think about how memory helps avoid slow disk access.

Describe the impact of setting max_connections too high or too low.

Consider client connections and server resources.

Practice

1. What is the main purpose of tuning MySQL server configuration settings?

easy

A. To backup the database automatically

B. To change the database schema structure

C. To improve server performance and handle more users efficiently

D. To write complex SQL queries

Solution

1. Step 1: Understand server tuning goal

   Server tuning adjusts settings like memory and cache to make the server faster and support more users.

2. Step 2: Differentiate from other tasks

   Changing schema, writing queries, or backups are different tasks unrelated to tuning configuration.

3. Final Answer:

   To improve server performance and handle more users efficiently -> Option C

4. Quick Check:

   Server tuning = performance improvement [OK]

Hint: Tuning means making server faster and handle more users [OK]

Common Mistakes:

• Confusing tuning with schema changes
• Thinking tuning is about writing queries
• Assuming tuning is for backups

2. Which of the following commands correctly changes a global MySQL server variable at runtime?

easy

A. SET GLOBAL max_connections = 200;

B. CHANGE GLOBAL max_connections TO 200;

C. UPDATE GLOBAL max_connections = 200;

D. ALTER GLOBAL max_connections = 200;

Solution

1. Step 1: Recall correct syntax for changing global variables

   The correct syntax uses SET GLOBAL variable_name = value;

2. Step 2: Check each option

   Only SET GLOBAL max_connections = 200; uses the correct SET GLOBAL syntax. Others use invalid keywords like CHANGE, UPDATE, ALTER.

3. Final Answer:

   SET GLOBAL max_connections = 200; -> Option A

4. Quick Check:

   SET GLOBAL = correct syntax [OK]

Hint: Use SET GLOBAL to change server variables at runtime [OK]

Common Mistakes:

• Using UPDATE or ALTER instead of SET
• Forgetting GLOBAL keyword
• Using TO instead of =

3. After running SET GLOBAL max_connections = 300;, what will the output of SHOW VARIABLES LIKE 'max_connections'; show?

medium

A. max_connections = 300

B. max_connections = 100 (default value)

C. Syntax error

D. max_connections = NULL

Solution

1. Step 1: Understand effect of SET GLOBAL

   SET GLOBAL changes the variable for the running server immediately.

2. Step 2: Check SHOW VARIABLES output

   SHOW VARIABLES LIKE 'max_connections' shows the current global value, which is now 300.

3. Final Answer:

   max_connections = 300 -> Option A

4. Quick Check:

   SET GLOBAL changes variable value immediately [OK]

Hint: SHOW VARIABLES shows current global values after SET GLOBAL [OK]

Common Mistakes:

• Thinking default value remains after SET GLOBAL
• Expecting syntax error from valid commands
• Assuming NULL means unset

4. You tried to run SET GLOBAL innodb_buffer_pool_size = 1073741824; but got an error. What is the most likely cause?

medium

A. The value is too small

B. You need SUPER privilege to change this variable

C. The variable name is misspelled

D. SET GLOBAL cannot change innodb variables

Solution

1. Step 1: Check privileges needed for changing global variables

   Changing global variables like innodb_buffer_pool_size requires SUPER privilege.

2. Step 2: Verify other options

   The variable name is correct, value is valid, and SET GLOBAL can change innodb variables if privileges allow.

3. Final Answer:

   You need SUPER privilege to change this variable -> Option B

4. Quick Check:

   SUPER privilege required for global changes [OK]

Hint: Changing global variables often needs SUPER privilege [OK]

Common Mistakes:

• Assuming syntax error means misspelling
• Thinking value size is the problem
• Believing SET GLOBAL can't change innodb variables

5. You want to increase the maximum number of allowed connections to 500 and verify the change without restarting the server. Which sequence of commands is correct?

hard

A. UPDATE max_connections = 500; SELECT max_connections;

B. SET max_connections = 500; SHOW STATUS LIKE 'max_connections';

C. ALTER SYSTEM SET max_connections = 500; SHOW VARIABLES;

D. SET GLOBAL max_connections = 500; SHOW VARIABLES LIKE 'max_connections';

Solution

1. Step 1: Identify correct command to change max_connections at runtime

   SET GLOBAL max_connections = 500; changes the setting immediately without restart.

2. Step 2: Verify the change

   SHOW VARIABLES LIKE 'max_connections'; displays the current value of max_connections.

3. Step 3: Check other options

   UPDATE and ALTER SYSTEM are invalid for this purpose; SET without GLOBAL affects session only; SHOW STATUS shows runtime stats, not variables.

4. Final Answer:

   SET GLOBAL max_connections = 500; SHOW VARIABLES LIKE 'max_connections'; -> Option D

5. Quick Check:

   SET GLOBAL + SHOW VARIABLES = correct sequence [OK]

Hint: Use SET GLOBAL then SHOW VARIABLES to change and check [OK]

Common Mistakes:

• Using UPDATE or ALTER SYSTEM commands
• Forgetting GLOBAL keyword in SET
• Using SHOW STATUS instead of SHOW VARIABLES