Skip to content
Discussion options

You must be logged in to vote

@javafanboy your suspicion holds up. I measured it on floci:2.3.0 and on nightly-10252026, and two parts of DynamoDB get slower as a table grows: writes, and Query. GetItem doesn't.

Setup: one table with pk (S) and sk (S) keys, items of about 250 bytes spread over 1,000 partitions, loaded with BatchWriteItem. At each size I timed 300 sequential calls of each operation from boto3 on the same host. PutItem and UpdateItem overwrite a random existing item, so the table doesn't grow while I'm measuring. Query always reads the same 20-item partition, so the result size never changes. Times are p50 in ms.

FLOCI_STORAGE_MODE=memory (the default), 2.3.0

items GetItem PutItem UpdateItem Query (2…

Replies: 4 comments 1 reply

Comment options

You must be logged in to vote
0 replies
Comment options

You must be logged in to vote
0 replies
Answer selected by hectorvent
Comment options

You must be logged in to vote
1 reply
@Mohith1612
Comment options

Comment options

You must be logged in to vote
0 replies
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
3 participants