Stay organized with collections
Save and categorize content based on your preferences.
MySQL | PostgreSQL | SQL Server
This page describes how to manage temporary binary log files and InnoDB redo log
files. This recommender is called
Reconfigure log settings.
Every day, this recommender analyzes the following:
Disk usage in the binary log and binary log statement caches. If more than
10% of your transactions and non-transactional statements write to temporary
files on disk, then Reconfigure log settings recommends that you should
increase the value of binlog_cache_size or binlog_stmt_cache_size to
improve performance.
For more information on increasing the value of binlog_cache_size, see
Cache memory consumption. For more information on
increasing the value of binlog_stmt_cache_size, see
binlog_stmt_cache_size.
The ratio of wait time versus write time for the InnoDB redo logs. This
recommender advises increasing the value of innodb_log_buffer_size if
transactions are waiting for the log buffer to flush.
For more information on increasing the value of innodb_log_buffer_size, see
[Buffer memory consumption](/sql/docs/mysql/
GET https://recommender.googleapis.com/v1/projects/PROJECT_ID/locations/LOCATION/recommenders/google.cloudsql.instance.PerformanceRecommender/recommendations
Replace the following:
PROJECT_ID: your project ID
LOCATION: a region where your instances are located, such as us-central1
View insights and detailed recommendations
To view insights and detailed recommendations, follow these steps:
Console
Do one of the following:
On the Performance Recommendations page, click the Performance
recommendations card and then click Reconfigure log settings.
The recommendation panel appears, which contains insights and
detailed recommendations for the instance.
On the Instances page, click Reconfigure log settings. The list of
instances displays only those instances for which the recommendation
applies.
GET https://recommender.googleapis.com/v1/projects/PROJECT_ID/locations/LOCATION/insightTypes/google.cloudsql.instance.PerformanceInsight/insights
Replace the following:
PROJECT_ID: your project ID
LOCATION: a region where your instances are located, such as us-central1
Apply the recommendation
To implement this recommendation, do one of the following:
Increase the value of either binlog_stmt_cache_size or binlog_cache_size.
For more information on increasing the value of binlog_stmt_cache_size, see
binlog_stmt_cache_size. For more
information on increasing the value of binlog_cache_size, see
Cache memory consumption.
Design your transactions to be small and use less of the binary log and binary
log statement caches.
Increase the value of innodb_log_buffer_size. For more information on
increasing the value of innodb_log_buffer_size, see
Buffer memory consumption.
Increase the persistent disk size so that you have enough parallel I/O
requests to improve ratio of read operations to write operations for the log
files.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-14 UTC."],[],[],null,["# Reconfigure log settings\n\n\u003cbr /\u003e\n\nMySQL \\| PostgreSQL \\| SQL Server\n\n\u003cbr /\u003e\n\n|\n| **Preview**\n|\n|\n| This feature is subject to the \"Pre-GA Offerings Terms\" in the General Service Terms section\n| of the [Service Specific Terms](/terms/service-terms#1).\n|\n| You can process personal data for this feature as outlined in the\n| [Cloud Data Processing\n| Addendum](/terms/data-processing-addendum), subject to the obligations and restrictions described in the agreement under\n| which you access Google Cloud.\n|\n| Pre-GA features are available \"as is\" and might have limited support.\n|\n| For more information, see the\n| [launch stage descriptions](/products#product-launch-stages).\n\nThis page describes how to manage temporary binary log files and InnoDB redo log\nfiles. This [recommender](/recommender/docs/recommenders) is called\n**Reconfigure log settings**.\n\nEvery day, this recommender analyzes the following:\n\n- Disk usage in the binary log and binary log statement caches. If more than\n 10% of your transactions and non-transactional statements write to temporary\n files on disk, then **Reconfigure log settings** recommends that you should\n increase the value of `binlog_cache_size` or `binlog_stmt_cache_size` to\n improve performance.\n\n For more information on increasing the value of `binlog_cache_size`, see\n [Cache memory consumption](/sql/docs/mysql/optimize-high-memory-usage#cache_memory_consumption). For more information on\n increasing the value of `binlog_stmt_cache_size`, see\n [`binlog_stmt_cache_size`](/sql/docs/mysql/flags#mysql-b).\n- The ratio of wait time versus write time for the InnoDB redo logs. This\n recommender advises increasing the value of `innodb_log_buffer_size` if\n transactions are waiting for the log buffer to flush.\n\n For more information on increasing the value of `innodb_log_buffer_size`, see\n \\[Buffer memory consumption\\](/sql/docs/mysql/\n\nPricing\n-------\n\nThe **Reconfigure log settings** recommender is in the *Standard*\n[Recommender pricing tier](/recommender/pricing).\n\nBefore you begin\n----------------\n\n[Enable the Recommender API](/recommender/docs/enabling).\n\n### Required roles and permissions\n\nTo get the permissions to view and work with insights and recommendations,\nensure that you have the required [Identity and Access Management (IAM) roles](/sql/docs/mysql/project-access-control#roles).\n\nFor more information about IAM roles, see [IAM basic and predefined roles reference](/iam/docs/understanding-roles) and [Manage access to projects, folders, and organizations](/iam/docs/granting-changing-revoking-access).\n\n\u003cbr /\u003e\n\nList the recommendations\n------------------------\n\nTo list the recommendations, follow these steps: \n\n### Console\n\nTo list recommendations about instance performance, follow these steps:\n\n1. Go to the **Cloud SQL Instances** page.\n\n[Go to Cloud SQL Instances](https://console.cloud.google.com/sql/instances)\n\n1. On the **Improve instance health by investigating issues and acting on recommendations** banner, click **Expand Details**.\n\nAlternatively, follow these steps:\n\n1. Go to the **Recommendation Hub** . See also [Find and apply recommendations with the Recommendations](/recommender/docs/recommendation-hub/identify-configuration-problems).\n\n [Go to the Recommendation Hub](https://console.cloud.google.com/home/recommendations/)\n2. In the **All recommendations** card, click **Performance** .\n\n### gcloud\n\nRun the [`gcloud recommender recommendations list`](/sdk/gcloud/reference/recommender/recommendations/list) command as follows: \n\n```\ngcloud recommender recommendations list \\\n--project=PROJECT_ID \\\n--location=LOCATION \\\n--recommender=google.cloudsql.instance.PerformanceRecommender \\\n--filter=recommenderSubtype=MYSQL_RECONFIG_TRANS_LOGS\n```\n\nReplace the following:\n\n- \u003cvar translate=\"no\"\u003ePROJECT_ID\u003c/var\u003e: your project ID\n- \u003cvar translate=\"no\"\u003eLOCATION\u003c/var\u003e: a region where your instances are located, such as `us-central1`\n\n### API\n\nCall the [`recommendations.list`](/recommender/docs/reference/rest/v1/projects.locations.recommenders.recommendations/list) method as follows: \n\n```\nGET https://recommender.googleapis.com/v1/projects/PROJECT_ID/locations/LOCATION/recommenders/google.cloudsql.instance.PerformanceRecommender/recommendations\n```\n\nReplace the following:\n\n- \u003cvar translate=\"no\"\u003ePROJECT_ID\u003c/var\u003e: your project ID\n- \u003cvar translate=\"no\"\u003eLOCATION\u003c/var\u003e: a region where your instances are located, such as `us-central1`\n\nView insights and detailed recommendations\n------------------------------------------\n\nTo view insights and detailed recommendations, follow these steps: \n\n### Console\n\nDo one of the following:\n\n- On the **Performance Recommendations** page, click the **Performance\n recommendations** card and then click **Reconfigure log settings**.\n The recommendation panel appears, which contains insights and\n detailed recommendations for the instance.\n\n- On the **Instances** page, click **Reconfigure log settings**. The list of\n instances displays only those instances for which the recommendation\n applies.\n\n### gcloud\n\nRun the [`gcloud recommender insights list`](/sdk/gcloud/reference/recommender/insights/list) command as follows: \n\n```\ngcloud recommender insights list \\\n--project=PROJECT_ID \\\n--location=LOCATION \\\n--insight-type=google.cloudsql.instance.PerformanceInsight \\\n--filter=insightSubtype=INSIGHT_SUBTYPE\n\n```\n\nReplace the following:\n\n- \u003cvar translate=\"no\"\u003ePROJECT_ID\u003c/var\u003e: your project ID\n- \u003cvar translate=\"no\"\u003eLOCATION\u003c/var\u003e: a region where your instances are located, such as `us-central1`\n- \u003cvar translate=\"no\"\u003eINSIGHT_SUBTYPE\u003c/var\u003e: set this parameter to one of the following:\n - `MYSQL_LOW_BINLOG_CACHE_SIZE`: display insights for the number of transactional binary logs using the on-disk cache for your instance\n - `MYSQL_LOW_BINLOG_STMT_CACHE_SIZE`: display insights for the number of non-transactional statement binary logs using the on-disk cache for your instance\n - `MYSQL_LOW_INNODB_LOG_BUFFER_SIZE`: display insights for the wait time compared to the write time for InnoDB redo logs\n\n### API\n\nCall the [`insights.list`](/recommender/docs/reference/rest/v1/projects.locations.insightTypes.insights/list) method as follows: \n\n```\n\nGET https://recommender.googleapis.com/v1/projects/PROJECT_ID/locations/LOCATION/insightTypes/google.cloudsql.instance.PerformanceInsight/insights\n\n```\n\nReplace the following:\n\n- \u003cvar translate=\"no\"\u003ePROJECT_ID\u003c/var\u003e: your project ID\n- \u003cvar translate=\"no\"\u003eLOCATION\u003c/var\u003e: a region where your instances are located, such as `us-central1`\n\nApply the recommendation\n------------------------\n\nTo implement this recommendation, do one of the following:\n\n- Increase the value of either `binlog_stmt_cache_size` or `binlog_cache_size`.\n\n For more information on increasing the value of `binlog_stmt_cache_size`, see\n [`binlog_stmt_cache_size`](/sql/docs/mysql/flags#mysql-b). For more\n information on increasing the value of `binlog_cache_size`, see\n [Cache memory consumption](/sql/docs/mysql/optimize-high-memory-usage#cache_memory_consumption).\n- Design your transactions to be small and use less of the binary log and binary\n log statement caches.\n\n- Increase the value of `innodb_log_buffer_size`. For more information on\n increasing the value of `innodb_log_buffer_size`, see\n [Buffer memory consumption](/sql/docs/mysql/optimize-high-memory-usage#buffer_memory_consumption).\n\n- Increase the persistent disk size so that you have enough parallel I/O\n requests to improve ratio of read operations to write operations for the log\n files.\n\n| **Note:** Increasing `binlog_stmt_cache_size`, `binlog_cache_size`, and `innodb_log_buffer_size` requires more memory. After increasing these flags, monitor the memory usage.\n\nWhat's next\n-----------\n\n- [Google Cloud recommenders](/recommender/docs/recommenders)"]]