Spanner Data Boost 是一项全代管式无服务器服务，可为受支持的 Spanner 工作负载提供独立的计算资源。Data Boost 使您可以执行分析查询和数据导出，且对预配的 Spanner 实例上的现有工作负载几乎没有影响。该服务由 Google 在区域一级管理的 Spanner 集群组成。对于请求 Data Boost 的符合条件的查询，Spanner 会以透明的方式将工作负载路由到这些服务器。符合条件的查询是指查询执行计划中的第一个运算符为分布式联合的查询。您无需更改这些查询即可使用 Data Boost。
[[["易于理解","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-11。"],[],[],null,["# Data Boost overview\n\nSpanner Data Boost is a fully managed, serverless service that provides\nindependent compute resources for supported Spanner workloads.\nData Boost lets you execute analytics queries and data exports\nwith near-zero impact to existing workloads on the provisioned\nSpanner instance. The service consists of Spanner\nclusters that Google manages at the region level. For eligible queries that\nrequest Data Boost, Spanner routes the workload to\nthese servers transparently. Eligible queries are those for which the first\noperator in the query execution plan is a distributed union. These queries don't\nhave to change to take advantage of Data Boost.\n\nData Boost is most impactful in the following scenarios where you\nwant to avoid negative impacts to the existing transactional system due to\nresource contention:\n\n- Ad hoc or infrequent queries that involve processing large amounts of data. A typical example is a [federated\n query](/bigquery/docs/spanner-federated-queries) from BigQuery to Spanner.\n- Reporting or data export jobs. An example is a Dataflow job to export Spanner data to Cloud Storage.\n\nThe following diagram illustrates how Data Boost coordinates with\nthe Spanner instance to provide independent compute resources.\n\nBenefits\n--------\n\nData Boost offers the following benefits:\n\n- Provides workload isolation. You can run supported queries against the latest data with near-zero impact on existing transactional workloads regardless of query complexity or amount of data processed.\n- Provides equal or better latency.\n- Prevents over-provisioning of Spanner instances just to support occasional analytics queries.\n- Offers a high degree of scalability with greater query parallelism that scales elastically with burst loads.\n- Provides comprehensive metrics, which let administrators identify the most expensive queries and determine the cost component to optimize. Administrators can then verify the impact of their optimizations by monitoring the query's serverless processing unit consumption in its next execution.\n- Requires no additional operational overhead. There is no extra service to manage, no capacity planning or provisioning, no need to wait for scaling, and no maintenance.\n\nPermissions\n-----------\n\nAny principal that runs a query or export that requests Data Boost\nmust have the `spanner.databases.useDataBoost` Identity and Access Management (IAM)\npermission. We recommend that you use the\n`Cloud Spanner Database Reader With DataBoost` (`roles/spanner.databaseReaderWithDataBoost`)\nIAM role.\n\nBilling and quotas\n------------------\n\nYou pay only for actual processing units used by queries that run on\nData Boost. Administrators can set limits on usage to avoid cost\noverruns.\n\nWhat's next\n-----------\n\n- [Run federated queries with Data Boost](/spanner/docs/databoost/databoost-run-queries)\n- [Export data with Data Boost](/spanner/docs/databoost/databoost-export)\n- [Use Data Boost in your applications](/spanner/docs/databoost/databoost-applications)\n- [Monitor Data Boost usage](/spanner/docs/databoost/databoost-monitor)\n- [Monitor and manage Data Boost quota usage](/spanner/docs/databoost/databoost-quotas)"]]
