DynamoDB high latency

Checks if any of the SCAN, QUERY, GET, PUT, or UPDATE calls to a DynamoDB table take more than 0.8 seconds to complete.

Dashbird continuously monitors and analyses your serverless applications to ensure reliability, cost and performance optimisation and alignment with the Well Architected Framework.

Product Features Start Free Trial

Severity: WARNING
Interval: 15 minutes
Time slot: last 1 hour

Metrics:
METRICS.DYNAMODB.DYNAMODB_LATENCY_SCAN
METRICS.DYNAMODB.DYNAMODB_LATENCY_QUERY
METRICS.DYNAMODB.DYNAMODB_LATENCY_ITEM_GET
METRICS.DYNAMODB.DYNAMODB_LATENCY_ITEM_PUT
METRICS.DYNAMODB.DYNAMODB_LATENCY_ITEM_UPDATE

Why do I see this?

Any of the SCAN, QUERY, GET, PUT or UPDATE calls to one of your DynamoDB tables take more than 0.8 seconds to complete.

What does this mean?

High latency can have different underlying reasons.

  • The service issuing the call is too far away geographically.
  • There are too many calls per second.
  • The code issuing the call is not optimized.

“For most atomic operations, such as GetItem and PutItem, you can expect an average latency in single-digit milliseconds. Latency for non-atomic operations, such as Query and Scan, depends on many factors, including the size of the result set and the complexity of the query conditions and filters.” – Amazon Docs.

How do I fix this?

You can learn how to fix latency related DynamoDB issues in the AWS docs.

This rule resolution is part of the Dashbird Serverless Well Architected Reports tool for AWS. Dashbird features a collection of rules and checks continuously applied to your infrastructure, surfacing ways to improve it.

Find and fix other errors and anomalies in DynamoDB.

Industry leader in serverless monitoring

Dashbird is a monitoring, debugging and intelligence platform designed to help serverless developers build, operate, improve, and scale their modern cloud applications on AWS environment securely and with ease.