How would a "hot" hash key affect throughout in practice on Amazon DynamoDB? -

first, here's support document dyanamodb giving guidance on how avoid "hot" hash key.

conceptually, hot hash key simple , (typically) straightforward avoid - documents give examples of how so. not asking hot hash key is.

what want know how throughout performance degrade given level of provisioned read/write units @ limit, is, when read/write activity focused on 1 (or few) partition(s). distributed hash key activity (uniform across partitions), dynamodb gives single millisecond response times. so, response times in worst case scenario?

here's post on aws asking related question gives specific use-case knowledge of answer matters.

dynamodb guarantee single millisecond response times, 'hot' hash key, but see lot throttled requests. , when seem have plenty of unspent provisioned throuput. because provisioned throuput gets divided number of partitions. don't know how many partitions there @ given time, varies how of provisioned throuput can spent single hashkey...