Dynamodb:删除是否算在读或写容量上? [英] Dynamodb: does delete count against read or write capacity?

查看:77
本文介绍了Dynamodb:删除是否算在读或写容量上?的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我无法在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)时间序列数据和访问模式部分= http://docs.amazonwebservices.com/amazondynamodb/latest/developerguide/BestPractices.html rel = noreferrer> 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)中的响应部分href = http://docs.amazonwebservices.com/amazondynamodb/latest/developerguide/API_DeleteItem.html rel = nor eferrer> DeleteItem API 列出返回值 ConsumedCapacityUnits 并引用写入容量单位:

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


操作消耗的写入容量单位数。
的值显示应用于预配置吞吐量的数字。有关
的更多信息,请参见 Amazon DynamoDB中的预置吞吐量

这篇关于Dynamodb:删除是否算在读或写容量上?的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆