다른 트래픽에 비해 Bigtable 테이블에 대한 일부 트래픽에 우선순위를 적용하려면 앱 프로필의 요청 우선순위를 지정하면 됩니다. Bigtable은 지정된 요청 우선순위를 사용해서 요청을 실행하는 순서를 결정합니다.
우선순위 수준
Bigtable에 전송되는 모든 요청에는 앱 프로필이 사용됩니다. 여기에는 Bigtable 인스턴스에 수신되는 요청의 처리 방법을 알려주는 설정이 저장됩니다. 작동 방식을 보려면 앱 프로필 개요를 참조하세요.
앱 프로필에서 다음 요청 우선순위를 지정할 수 있습니다.
높음
보통
낮음
높은 우선순위 요청은 낮은 우선순위 요청보다 실행 가능성이 높습니다.
우선순위를 지정하지 않으면 모든 요청이 기본적으로 높은 우선순위로 고려됩니다.
워크로드 유형의 기본 우선순위 수준
지연 시간에 민감하고 경로를 제공하는 워크로드에 사용하는 앱 프로필에 높은 우선순위를 지정합니다.
높은 우선순위 요청의 성능에 영향을 주지 않고 실행하려는 워크로드에 사용하는 앱 프로필에는 중간 또는 낮은 우선순위를 지정합니다. 예를 들어 일괄 읽기 분석은 해당 트래픽이 높은 우선순위로 지정한 애플리케이션 제공 트래픽과 경합하지 않도록 낮은 우선순위를 지정할 수 있습니다.
우선순위가 높음, 중간, 낮음으로 혼합된 트래픽을 전송할 때는 클러스터의 CPU 사용률을 권장되는 최댓값보다 낮게 유지해야 합니다.
CPU 사용률을 낮게 유지하면 우선순위가 낮은 요청이라도 리소스 부족 문제가 발생하지 않습니다.
권장 최댓값을 검토하려면 용량 계획을 참조하세요.
요청 우선순위 구성
요청 우선순위를 지정하려면 Google Cloud CLI를 사용해야 합니다. gcloud CLI가 최신 버전인지 확인하려면 다음을 실행합니다.
gcloud components update
gcloud CLI 명령어를 실행할 때는 다음을 바꿉니다.
APP_PROFILE_ID - 앱 프로필의 영구 식별자입니다.
INSTANCE_ID - 인스턴스의 영구 식별자입니다.
PRIORITY_LEVEL - 앱 프로필이 사용하는 우선순위 수준입니다. 허용되는 값은 PRIORITY_HIGH, PRIORITY_MEDIUM 또는 PRIORITY_LOW입니다.
[[["이해하기 쉬움","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-09-04(UTC)"],[[["\u003cp\u003eBigtable allows you to prioritize traffic to a table by specifying request priorities within app profiles, which include options for High, Medium, and Low.\u003c/p\u003e\n"],["\u003cp\u003eHigher priority requests are generally processed before lower priority ones, and all requests are considered high priority by default if no priority is specified.\u003c/p\u003e\n"],["\u003cp\u003eYou should assign high priority to app profiles used for latency-sensitive workloads, and medium or low priority to those used for background tasks like batch read analytics.\u003c/p\u003e\n"],["\u003cp\u003eThe \u003ccode\u003egcloud\u003c/code\u003e CLI is required to configure request priorities, and you can set the priority during the creation of an app profile or update it later.\u003c/p\u003e\n"],["\u003cp\u003eIt is recommended to monitor the CPU utilization of clusters when utilizing traffic with different priorities, ensuring they remain under the maximum threshold to prevent lower priority requests from being starved.\u003c/p\u003e\n"]]],[],null,["Configure request priorities\n\nTo prioritize some traffic to a Bigtable table over other traffic, you\ncan specify an app profile's *request priority*. Bigtable uses the\nspecified request priority to determine the order in which it executes requests.\n\nPriority levels\n\nAll requests sent to Bigtable use an *app profile* , which stores\nsettings that tell your Bigtable instance how to handle incoming\nrequests. To understand how they work, see\n[App profiles overview](/bigtable/docs/app-profiles).\n\nYou can specify the following request priorities in an app profile:\n\n- High\n- Medium\n- Low\n\nHigher priority requests are likely to run before lower priority requests.\n\nIf you don't specify a priority, all requests are considered high priority by\ndefault.\n| **Note:** Bigtable's scheduling of high priority requests favors operations that take less time to complete, such as simple, single-row read requests that return small payloads on the order of kilobytes.\n\nBase priority level on workload type\n\nSpecify high priority for app profiles that you use for latency-sensitive,\nserving-path workloads.\n\nSpecify medium or low priority for app profiles that you use for workloads that\nyou want to run without impacting the performance of high priority requests. For\nexample, you can make batch read analytics a low priority so that traffic\ndoesn't compete with application-serving traffic that you designate as high\npriority.\n\nSpecify low priority for batch jobs that use [batch write flow\ncontrol](/bigtable/docs/writes#flow-control).\n\nMonitor CPU utilization\n\nWhen you send a mix of high, medium, or low priority traffic, be sure to keep\nyour clusters' CPU utilization below the recommended maximum values.\nMaintaining lower CPU utilization ensures that lower priority requests aren't\n[starved](https://en.wikipedia.org/wiki/Starvation_(computer_science)).\nTo review the recommended maximums, see [Plan your capacity](/bigtable/docs/performance#planning-your-capacity).\n\nConfigure request priorities\n\nYou must use the Google Cloud CLI to specify request\npriorities. To ensure that you have the most recent version of the\ngcloud CLI, run the following: \n\n gcloud components update\n\nWhen you execute the gcloud CLI commands, replace the following:\n\n- \u003cvar translate=\"no\"\u003eAPP_PROFILE_ID\u003c/var\u003e - The permanent identifier for the app profile.\n- \u003cvar translate=\"no\"\u003eINSTANCE_ID\u003c/var\u003e - The permanent identifier for the instance.\n- \u003cvar translate=\"no\"\u003ePRIORITY_LEVEL\u003c/var\u003e - The priority level that the app profile uses. Accepted values are `PRIORITY_HIGH`, `PRIORITY_MEDIUM`, or `PRIORITY_LOW`.\n\nSpecify a request priority when creating a new app profile\n\nTo create an app profile with a specified request priority, run the following\ncommand. For the complete list of additional positional arguments and flags that\nyou can use with this command, see [`gcloud bigtable app-profiles\ncreate`](/sdk/gcloud/reference/bigtable/app-profiles/create). \n\n gcloud bigtable app-profiles create \u003cvar translate=\"no\"\u003eAPP_PROFILE_ID\u003c/var\u003e \\\n --instance=\u003cvar translate=\"no\"\u003eINSTANCE_ID\u003c/var\u003e \\\n --route-any \\\n --priority=\u003cvar translate=\"no\"\u003ePRIORITY_LEVEL\u003c/var\u003e\n\nAdd or change an app profile's request priority\n\nTo update the priority of an existing app profile, run the following\ncommand. For the complete list of additional positional arguments and flags that\nyou can use with this command,\nsee [`gcloud bigtable app-profiles\nupdate`](/sdk/gcloud/reference/bigtable/app-profiles/update). \n\n gcloud bigtable app-profiles update \u003cvar translate=\"no\"\u003eAPP_PROFILE_ID\u003c/var\u003e \\\n --instance=\u003cvar translate=\"no\"\u003eINSTANCE_ID\u003c/var\u003e \\\n --route-any \\\n --priority=\u003cvar translate=\"no\"\u003ePRIORITY_LEVEL\u003c/var\u003e\n\nTo stop using request priorities for a table, run the command to set the\npriority to `PRIORITY_HIGH` for every app profile that your applications use to\nsend requests to the table.\n\nWhat's next\n\n- [See examples of replication settings](/bigtable/docs/replication-settings)\n- [Review write-request types](/bigtable/docs/writes)"]]
