[[["易于理解","easyToUnderstand","thumb-up"],["解决了我的问题","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["很难理解","hardToUnderstand","thumb-down"],["信息或示例代码不正确","incorrectInformationOrSampleCode","thumb-down"],["没有我需要的信息/示例","missingTheInformationSamplesINeed","thumb-down"],["翻译问题","translationIssue","thumb-down"],["其他","otherDown","thumb-down"]],["最后更新时间 (UTC)：2025-08-18。"],[],[],null,["# Custom performance\n\nThis page discusses custom performance settings for your Filestore\ninstances.\n\nRead and write IOPS\n-------------------\n\nYou can use 100% of IOPS purchased for your file system for read and write operations combined.Read and write operations have different weights, meaning that a write operation consumes more IOPS than a read operation.\nFor example, if your file system uses 33% of its purchased IOPS for read operations, it can simultaneously use up to 67% of its purchased IOPS for write operations.\n\nCustom performance supports up to 100 client connections per 1,000 purchased IOPS, regardless of the capacity range or service tier being regional or zonal.\n\nIOPS accrued from replicated data, such as [backup](/filestore/docs/backups) operations, don't count towards user-purchased IOPS.\n\n### Example IOPS calculation\n\nAssuming you have purchased 4,000 IOPS:\n\n- If you want to use them strictly for read IOPS, you would have access to a maximum of 4,000 read IOPS.\n- If you want to use them strictly for write IOPS, you would have access to a maximum of 1,200 write IOPS.\n- If you want to use 900 IOPS for write operations, it will effectively use 3,000 of your IOPS budget, leaving 1,000 IOPS for read operations.\n\nIf you need more IOPS or throughput, you can increase your purchased IOPS rate.\n\nConfigure custom performance\n----------------------------\n\nYou can set custom performance for zonal and regional instances\nthat already support it. Basic tiers don't support this feature.\n\nCustom performance instances are billed differently than instances where custom performance is not configured. For details, see [Filestore pricing](/filestore/pricing).\n\nYou have the following options to configure custom performance:\n\n- Set an IOPS per TiB ratio where IOPS scale linearly with the instance's size.\n- Set a fixed IOPS rate. The rate is steady, regardless of instance size.\n\n| **Note:** When you enable custom performance in Google Cloud console and don't provide any specific configuration, a default, recommended IOPS rate is suggested for this instance. After you activate custom performance for an instance and save your settings, you can't deactivate it for that instance.\n\nFor details on setting custom performance, see [creating instances](/filestore/docs/creating-instances#define-performance).\n\n### Check custom performance status\n\nIf you want to the check the custom performance status, follow these instructions: \n\n### Google Cloud console\n\n[Go to the Filestore Instances page](https://console.cloud.google.com/filestore/instances)\n\n1. Click the **Instance ID** to open the **Instance Details** page.\n2. Go to the **Overview** tab and look for a **Custom Performance** entry.\n\n - **Not supported** means that custom performance is not supported for a specific instance. For example, when you create a basic tier instance, or when the instance was created before the feature was launched.\n - **Enabled** means that custom performance is supported and active for this instance.\n - **Disabled** means that custom performance is supported but not enabled for this instance.\n\n### gcloud\n\nGet information about a Filestore instance by running the\n[`instances describe`](/sdk/gcloud/reference/filestore/instances/describe)\ncommand: \n\n gcloud filestore instances describe \u003cvar translate=\"no\"\u003eINSTANCE_ID\u003c/var\u003e --project=\u003cvar translate=\"no\"\u003ePROJECT_ID\u003c/var\u003e --location=\u003cvar translate=\"no\"\u003eLOCATION\u003c/var\u003e\n\nThe output might vary depending on the instance settings. The following is an example output: \n\n createTime: '2021-10-11T17:28:23.340943077Z'\n customPerformanceSupported: true\n fileShares:\n - capacityGb: '1024'\n name: vol1\n kmsKeyName: projects/example-project/locations/us-central1/keyRings/example-ring/cryptoKeys/example-key\n labels:\n key:val\n name: projects/yourproject/locations/us-central1/instances/nfs-server\n networks:\n - ipAddresses:\n - 10.0.0.2\n network: default\n reservedIpRange: 10.0.0.0/26\n performanceConfig:\n iopsPerTb:\n maxIopsPerTb: '17000'\n performanceLimits:\n maxIops: '17000'\n maxReadIops: '17000'\n maxReadThroughputBps: '417792000'\n maxWriteIops: '5100'\n maxWriteThroughputBps: '139264000'\n state: READY\n tier: REGIONAL\n\n- If `customPerformanceSupported` parameter is present and set to `true` it means that custom performance is supported for this instance. If the flag is not present, custom performance is not supported.\n\n- If `performanceConfig` parameter is present, it means that custom performance is enabled for this instance.\n\n### REST API\n\n1. Have gcloud CLI [installed and initialized](/sdk/docs/install), which lets\n you generate an access token for the `Authorization` header.\n\n\n2.\n\n Use [`cURL`](http://curl.haxx.se/) to call the [Filestore API](/filestore/docs/reference/rest/v1/projects.locations.instances/get): \n\n ```\n curl -s \\\n --header \"Authorization: Bearer $(gcloud auth print-access-token)\" \\\n --header \"Content-Type: application/json\" \\\n GET \"https://file.googleapis.com/v1beta1/projects/PROJECT/locations/LOCATION/instances/INSTANCE_NAME\"\n ```\n\n Where:\n - \u003cvar translate=\"no\"\u003ePROJECT\u003c/var\u003e is the name of the project where your instance is located. For example, `my-project`.\n - \u003cvar translate=\"no\"\u003eLOCATION\u003c/var\u003e is the location where your instance resides. For example, `us-central1-a`.\n - \u003cvar translate=\"no\"\u003eINSTANCE_NAME\u003c/var\u003e is the name of the instance you want to view. For example, `nfs-server`.\n\n If custom performance is supported and configured for the provided instance, the response will include the following parameters: \n\n \"customPerformanceSupported\": true,\n \"performanceConfig\": {\n \"fixedIops\": {\n \"maxIops\": \"9000\"\n }\n },\n \"performanceLimits\": {\n \"maxReadIops\": \"9000\",\n \"maxWriteIops\": \"2700\",\n \"maxReadThroughputBps\": \"221184000\",\n \"maxWriteThroughputBps\": \"73728000\",\n \"maxIops\": \"9000\"\n }\n\nCustom performance limits\n-------------------------\n\nThe following table lists the performance limits based on minimum and maximum capacity values. These values determine the maximum expected read and write IOPS and throughput.\n\nFor more information, see the [read and write IOPS](/filestore/docs/custom-performance#iops) section of this document.\n\n| **Note:** For details about performance limits when custom performance is not activated, see [performance limits](/filestore/docs/performance).\n\nMonitoring\n----------\n\nTo monitor instance IOPS usage, you can use the **Metrics Explorer** to view the following metrics: `read_ops_count`, `write_ops_count`, and `metadata_ops_count`.\n\nFor more information, see [monitoring instances](/filestore/docs/monitoring-instances).\n\nWhat's next\n-----------\n\n- [Scale capacity](/filestore/docs/scale)"]]
