問題描述

我無法在 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:刪除是否計入讀取或寫入容量?的文章就介紹到這了，希望我們推薦的答案對大家有所幫助，也希望大家多多支持html5模板網！