问题描述

我无法在 Amazon 中找到关于此的文档:有人知道删除操作是否会影响您的读取或写入容量?

I haven't able to find documentation within Amazon on this: does anyone know if the delete operation counts against your read or write capacity?

我曾预计它会算作写入"，但我在测试中看到的行为似乎表明相反.有人可以确认吗?

I had expected it would count as a "write", but the behavior I'm seeing in testing seems to indicate the opposite. Can someone confirm this?

推荐答案

好问题 - 虽然这似乎没有明确指定，但仍然有两个强烈的提示可以被视为写入操作(正如人们所期望的那样):

Good question - while this doesn't seem to be specified explicitly, there are still two strong hints towards being counted as a write operation (as one would expect indeed):

1) 时间序列数据和访问模式部分>Amazon DynamoDB 中的预置吞吐量指南 解决了高效删除问题并指代受影响的写入吞吐量:

1) Section Time Series Data and Access Patterns within Provisioned Throughput Guidelines in Amazon DynamoDB addresses efficient deletion and refers to affected write throughput:

删除整个表比删除更有效一个接一个的项目，这实际上使写入吞吐量翻了一番您执行的删除操作与放置操作一样多.

Deleting an entire table is significantly more efficient than removing items one-by-one, which essentially doubles the write throughput as you do as many delete operations as put operations.

2) DeleteItem API<中的响应部分/a> 列出返回值 ConsumedCapacityUnits 并指代写入容量单位:

2) Section Responses within the DeleteItem API lists the return value ConsumedCapacityUnits and refers to write capacity units:

操作消耗的写入容量单位数.这value 显示应用于您的预置吞吐量的数字.为了更多信息请参阅Amazon DynamoDB 中的预置吞吐量.

The number of write capacity units consumed by the operation. This value shows the number applied toward your provisioned throughput. For more information see Provisioned Throughput in Amazon DynamoDB.

这篇关于Dynamodb:删除是否计入读取或写入容量?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持跟版网！