GET https://recommender.googleapis.com/v1beta1/projects/PROJECT-ID/locations/LOCATION/recommenders/google.cloudsql.instance.PerformanceRecommender.MySqlHighNumberOfTablesBestPractice/recommendations
다음을 바꿉니다.
PROJECT_ID: 프로젝트 ID입니다.
LOCATION: 리전(예: us-central1)
추천자에서 테이블 수가 많은 인스턴스를 감지하면 다른 성능 권장사항과 함께 테이블에 나열합니다.
행마다 인스턴스 ID, 간단한 권장사항, 데이터베이스 엔진, 위치, 마지막 새로고침 날짜가 표시됩니다.
통계 및 자세한 권장사항 보기
Google Cloud 콘솔, gcloud CLI 또는 Recommender API를 사용하여 테이블 수가 많은 인스턴스에 대한 통계와 자세한 권장사항을 확인할 수 있습니다.
콘솔
Google Cloud 콘솔을 사용하여 성능 기준점에 근접한 인스턴스에 대한 통계와 자세한 권장사항을 보려면 인스턴스 목록에서 권장사항 링크를 클릭합니다.
GET https://recommender.googleapis.com/v1beta1/projects/PROJECT-ID/locations/LOCATION/insightTypes/google.cloudsql.instance.PerformanceRecommender.MySqlHighNumberOfTables/insights
다음을 바꿉니다.
PROJECT_ID: 프로젝트 ID입니다.
LOCATION: 리전(예: us-central1)
다음 표에는 성능 향상을 위해 Cloud SQL 열린 테이블 수가 많은 추천자에 대한 개방형 테이블 추천자가 생성하는 통계 및 권장사항이 나와 있습니다.
하위 유형은 gcloud CLI 및 API 결과에 표시됩니다.
Insight
권장사항
이 인스턴스의 테이블 수가 테이블 수 50,000개 SLA 한도의 80% 보다 많거나 같습니다.
하위 유형: MYSQL_HIGH_NUMBER_OF_TABLES
테이블 수를 줄여 Cloud SQL 인스턴스 성능을 개선하세요.
하위 유형: MYSQL_HIGH_NUMBER_OF_TABLES_BEST_PRACTICE
인스턴스를 수정하여 vCPU 수를 최소 32개 코어로, 메모리 크기를 최소 200GB로 늘립니다.
이렇게 하면 인스턴스의 테이블 한도가 50,000개에서 500,000개로 증가합니다.
불필요한 테이블을 삭제합니다.
DROP TABLE TABLE_NAME;
다음을 바꿉니다.
TABLE_NAME: 삭제할 테이블의 이름입니다.
데이터베이스를 인스턴스 여러 개로 분할하여 인스턴스당 테이블 수를 줄여 각 인스턴스의 테이블 수를 권장 한도 내로 유지합니다.
테이블 수를 즉시 줄일 수 없는 경우에는 innodb_file_per_table 플래그를 OFF로 설정하여 인스턴스 수가 많을 때 인스턴스가 영향을 받을 가능성을 줄이세요. innodb_file_per_table 플래그의 값을 사용 중지하려면 데이터베이스 플래그 구성을 참조하세요.
하지만 이 설정은 인스턴스에 SLA 규정 준수를 다시 적용하지 않습니다.
이 운영 가이드라인을 참조하세요.
일반 테이블스페이스를 사용하여 테이블을 만들거나 기존 테이블을 일반 테이블스페이스로 이동합니다.
자세한 내용은 일반 테이블스페이스에 대한 MySQL 문서를 참조하세요.
[[["이해하기 쉬움","easyToUnderstand","thumb-up"],["문제가 해결됨","solvedMyProblem","thumb-up"],["기타","otherUp","thumb-up"]],[["이해하기 어려움","hardToUnderstand","thumb-down"],["잘못된 정보 또는 샘플 코드","incorrectInformationOrSampleCode","thumb-down"],["필요한 정보/샘플이 없음","missingTheInformationSamplesINeed","thumb-down"],["번역 문제","translationIssue","thumb-down"],["기타","otherDown","thumb-down"]],["최종 업데이트: 2025-08-19(UTC)"],[],[],null,["# Manage high number of tables\n\n\u003cbr /\u003e\n\nMySQL \\| PostgreSQL \\| SQL Server\n\n\u003cbr /\u003e\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| 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\nThe Cloud SQL high-number-of-tables [recommender](/recommender/docs/overview) helps you detect instances\nwhose table count is too high and close to the SLA limit. It then provides recommendations\non how to optimize such instances and improve instance performance.\n\nThis page describes how the high-number-of-tables recommender works and how\nyou can use it.\n\nHow it works\n------------\n\nIf you have 50,000 or more database tables on a single instance, it could result\nin the instance becoming unresponsive or unable to perform maintenance operations,\nand the instance is not covered by the SLA.\n\nThe Cloud SQL high-number-of-tables recommender analyzes metrics for the number\nof tables on a Cloud SQL MySQL instance. If the number of tables is larger than or\nequal to 80% of the SLA limit, which allows for 50,000 tables, the instance is considered\nto have a high number of tables.\n| **Note:** Recommendations are generated daily.\n\nPricing\n-------\n\nThe Cloud SQL high-number-of-open-tables recommender is in the *Standard* [Recommender pricing tier](/recommender/pricing).\n\nBefore you begin\n----------------\n\nBefore you can view recommendations and insights, do the following:\n\n- To get the permissions to view and work with insights and recommendations, ensure that you have the required [roles](/sql/docs/mysql/project-access-control#roles).\n\n For more information about roles, see [understanding roles](/iam/docs/understanding-roles) and [granting IAM permissions](/iam/docs/granting-changing-revoking-access).\n-\n\n\n Enable the Recommender API.\n\n\n [Enable the API](https://console.cloud.google.com/flows/enableapi?apiid=recommender.googleapis.com)\n\nList Improve Instance Performance recommendations\n-------------------------------------------------\n\nYou can list the Improve Instance Performance recommendations by\nusing the Google Cloud console, [gcloud CLI](/sdk/gcloud), or the Recommender API.\n\nThe improve instance performance recommendations are shown only if you have instances that\nare nearing performance threshold limits. \n\n### Console\n\nTo list recommendations about instance performance by using the\nGoogle Cloud console, 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)\n2. Click **View all** on the Manage high number of tables recommendations banner.\n\nAlternatively, follow these steps:\n\n1. Go to the **Recommendation Hub** . See also [Getting started with Recommendation Hub](/recommender/docs/recommendation-hub/identify-configuration-problems).\n\n [Go to the Recommendation Hub](https://console.cloud.google.com/home/recommendations/)\n2. In the **Improve Cloud SQL Instance Performance** card, click **View all**.\n\n3. Select the instances with **Manage high number of tables** recommendation.\n\n### gcloud CLI\n\nTo list Improve Instance Performance recommendations by using `gcloud CLI`, run the\n[`gcloud recommender recommendations list`](/sdk/gcloud/reference/recommender/recommendations/list)\ncommand 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_HIGH_NUMBER_OF_TABLES_BEST_PRACTICE\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, such as `us-central1`\n\n### API\n\nTo list Improve Instance Performance recommendations by using the\n[Recommendations API](/recommender/docs/using-api), call the\n[`recommendations.list`](/recommender/docs/reference/rest/v1beta1/projects.locations.recommenders.recommendations/list)\nmethod as follows: \n\n```\nGET https://recommender.googleapis.com/v1beta1/projects/PROJECT-ID/locations/LOCATION/recommenders/google.cloudsql.instance.PerformanceRecommender.MySqlHighNumberOfTablesBestPractice/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, such as `us-central1`.\n\nIf the recommender detects instances with high number of tables, it lists them in a\ntable with other performance recommendations.\nEach row shows the instance ID, a brief recommendation, database engine, the location, and the last refresh date.\n\nView insights and detailed recommendations\n------------------------------------------\n\nYou can view insights and detailed recommendations about instances\nthat have a high number of tables by using the Google Cloud console,\n`gcloud CLI`, or the Recommender API. \n\n### Console\n\nTo view insights and detailed recommendations about instances that are close to the performance threshold by using the Google Cloud console, click the recommendation\nlink in the list of instances.\n\n### gcloud CLI\n\nTo view insights and detailed recommendations about instances that are close to the performance threshold by using `gcloud CLI`, run the\n[`gcloud recommender insights list`](/sdk/gcloud/reference/recommender/insights/list)\ncommand 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=MYSQL_HIGH_NUMBER_OF_TABLES\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, such as `us-central1`.\n\n### API\n\nTo view insights and detailed recommendations about instances that are close to the performance threshold\nby using the [Recommendations API](/recommender/docs/using-api),\ncall the [`insights.list`](/recommender/docs/reference/rest/v1beta1/projects.locations.insightTypes.insights/list)\nmethod as follows: \n\n```\nGET https://recommender.googleapis.com/v1beta1/projects/PROJECT-ID/locations/LOCATION/insightTypes/google.cloudsql.instance.PerformanceRecommender.MySqlHighNumberOfTables/insights\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, such as `us-central1`.\n\nThe following table lists the insight and recommendation that the Cloud SQL\nhigh-number-of-open-tables recommender generates to help you improve performance.\nThe subtypes are visible in the `gcloud CLI` and API results.\n\nApply recommendations\n---------------------\n\nEvaluate the recommendations carefully and do any of the following:\n\n- To examine the instance, click **View instance** . See [Optimize the performance of your instance](#optimize-performance)\n and follow the recommendations.\n\n- To dismiss the recommendation so that it's de-emphasized and appears dimmed,\n click **Dismiss**.\n\n- To close the panel without applying or dismissing the recommendation, click\n **Cancel**.\n\n### Optimize the performance of your instance\n\n- [Edit](/sql/docs/mysql/edit-instance) your instance to increase the number of vCPUs\n to at least 32 cores and the memory size to at least 200 GB.\n This increases the instance's [table limit](/sql/docs/mysql/quotas#table_limit) from 50,000 to 500,000.\n\n | **Caution:** This operation can lead to an increase in cost. Additionally, it triggers a restart, which can cause downtime on the instance.\n- Drop unnecessary tables:\n\n ```\n DROP TABLE TABLE_NAME; \n ```\n\n Replace the following:\n - \u003cvar translate=\"no\"\u003eTABLE_NAME\u003c/var\u003e: Name of the table you intend to drop.\n- Reduce the number of tables per instance by splitting the database across multiple instances to keep the number of tables in each\n instance within the recommended limits.\n\n- If you cannot immediately reduce the number of tables, you can reduce the likelihood\n of your instance being impacted by the high table\n count by setting the `innodb_file_per_table` flag to OFF. To turn off the value of\n the `innodb_file_per_table` flag, see [Configure a database flag](/sql/docs/mysql/flags?hl=en#config).\n However, this setting does not bring the instance back into SLA compliance.\n See these [operational guidelines](/sql/docs/mysql/operational-guidelines?hl=en#tables).\n\n- Use a general tablespace to create tables or move existing tables to a general tablespace.\n To learn more, see [MySQL documentation on general tablespaces](https://dev.mysql.com/doc/refman/8.0/en/general-tablespaces.html).\n\nWhat's next\n-----------\n\n- [Increase the table open cache size](/sql/docs/mysql/recommender-high-number-of-open-tables)\n- [Monitor disk availability](/sql/docs/mysql/using-ood-recommender)\n- [Identify idle Cloud SQL instances](/sql/docs/mysql/recommender-sql-idle)\n- [Reduce overprovisioned Cloud SQL instances](/sql/docs/mysql/recommender-sql-overprovisioned)\n- Explore [Google Cloud recommenders](/recommender/docs/recommenders)"]]
