[[["容易理解","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-09 (世界標準時間)。"],[[["\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)"]]
