You can view and modify certain parameters and query parameter modification logs in TencentDB for MySQL console.
Note:You can modify the parameters of both source and read-only instances in the console in the same way as detailed below.
Note:
- If you select Immediate execution, the parameter modification task will be executed and take effect immediately.
- If you select During maintenance time, the parameter modification task will be executed and take effect during this time. For more information, see Setting Instance Maintenance Window.
Note:
- If you select Immediate execution, the parameter modification task will be executed and take effect immediately.
- If you select During maintenance time, the parameter modification task will be executed and take effect during this time. For more information, see Setting Instance Maintenance Window.
Note:
- If you select Immediate execution, the parameter modification task will be executed and take effect immediately.
- If you select During maintenance time, the parameter modification task will be executed and take effect during this time. For more information, see Setting Instance Maintenance Window.
Note:
- If you select Immediate execution, the parameter modification task will be executed and take effect immediately.
- If you select During maintenance time, the parameter modification task will be executed and take effect during this time. For more information, see Setting Instance Maintenance Window.
For more information, see Managing Parameter Template > Applying a Parameter Template to a Database.
Note:
- If you select Immediate execution, the parameter modification task will be executed and take effect immediately.
- If you select During maintenance time, the parameter modification task will be executed and take effect during this time. For more information, see Setting Instance Maintenance Window.
You can use a formula to set the instance parameters. To do so, set the parameters related to the instance specification as a formula, and when the instance specification is changed, the parameter values in the formula will be dynamically changed accordingly and still take effect after the specification change. In this way, the instance is always in the optimal state for running business smoothly.
Taking the {DBinitMemory\*786432}
value of the parameter innodb_buffer_pool_size
as an example, when the DBinitMemory
in the instance specification is changed, the parameter configuration here doesn't need to be modified, and the value of innodb_buffer_pool_size
will be changed automatically.
Expression syntax is supported as follows:
Supported Type | Description | Sample |
---|---|---|
Variable | DBinitMemory: Instance memory in MB (integer type). For example, if the memory size of the instance is 4000 MB, the value of DBinitMemory is 4000. DBInitCpu: The number of CPU cores of the instance (integer type). For example, if the instance specification is 8 cores, the value of DBInitCpu is 8. | {DBinitMemory * 786432} = memory size (DBinitMemory) * percentage (75% by default) * 1024 * 1024 (unit conversion) |
Operator | Formula syntax: It should be enclosed in braces ({} ). Division operator (/): It divides the dividend by the divisor and returns an integer quotient. If the calculation result is a decimal number, only the integer part will be retained. Decimal numbers are not supported; for example, {MIN(DBInitMemory/4+500,1000000)} instead of {MIN(DBInitMemory0.25+500,1000000)} is supported. Multiplication operator (*): It multiplies two numbers and returns an integer product. If the calculation result is a decimal number, only the integer part will be retained. Decimal number calculation is not supported. |
- |
Function | MAX(): It returns the greatest value in an integer or parameter formula list. MIN(): It returns the smallest value in an integer or parameter formula list. | {MAX(DBInitCpu/2,4)} |
Note:TencentDB for MySQL continuously optimizes parameter settings. The following lists only certain parameters that support parameter formula. You can learn more about parameter formulas in the parameter template in the console.
Parameter | Description | Default Formula |
---|---|---|
thread_pool_size | The number of thread groups in the thread pool. The default value means that the number of thread groups is the same as the number of CPU cores. | {MIN(DBInitCpu,64)} |
table_open_cache_instances | The number of partitions where MySQL caches table handles. | {MIN(DBInitMemory/1000,16)} |
table_open_cache | The size of the table descriptor, which can reduce the file open/close times. | {MAX(DBInitMemory*512/1000,2048)} |
table_definition_cache | The number of opened table cache instances. | {MAX(DBInitMemory*512/1000,2048)} |
max_connections | Max connections. | {MIN(DBInitMemory/4+500,1000000)} |
join_buffer_size | The minimum size of the buffer used for normal index scans, range index scans, and table joins that perform full-table scans. | {MIN(DBInitMemory*128,262144)} |
innodb_write_io_threads | The number of I/O threads in InnoDB used for write operations. | {MAX(DBInitCpu/2,4)} |
innodb_read_io_threads | The number of I/O threads in InnoDB used for read operations. | {MAX(DBInitCpu/2,4)} |
innodb_buffer_pool_instances | The number of partitions in the InnoDB buffer pool. | {MIN(DBInitMemory/2000,16)} |
innodb_buffer_pool_size | The size of the buffer pool in bytes, i.e., the memory zone where InnoDB caches tables and index data. | {DBInitMemory*786432} |
Before you confirm the parameter modification, the Modify Parameters dialog box will pop up for you to select a custom time window for the modification to take effect.
Note:If you select During maintenance time, the parameter modification task will be executed and take effect during this time. For more information, see Setting Instance Maintenance Window.
If a parameter modification task (to be executed during maintenance window) has been submitted but you want to cancel it, you can select Task List on the left sidebar in the console, locate the task, and click Cancel in the Operation column. You can cancel a task only before it is executed. The task status should be Waiting for execution.
Was this page helpful?