All posts
Serverless

Lambda Cold Starts With Postgres, RDS Proxy and DynamoDB, Measured: VPC or Not, 200 at Once

By

November 9, 2026

7 min read

Node.js 22 functions on arm64 took 570–650 ms end to end on a cold start, whether they talked to Postgres directly, through RDS Proxy, or to DynamoDB, and a function in a VPC was no slower than one outside it. Bursts of 200 simultaneous cold starts all succeeded. Warm, RDS Proxy added about 3 ms per query.

Benchmark
Postgres Performance
AWS Lambda
RDS Proxy
DynamoDB
Postgres, direct571 ms24 msPostgres via RDS Proxy569 ms23 msDynamoDB, in a VPC648 ms22 msDynamoDB, no VPC623 ms21 ms

Cold start

Warm

Median time for one invocation as seen by the caller (log scale). Our measurements, November 2026. Node.js 22, arm64, 1 GB.

The data
Cold startWarm
Postgres, direct571 ms24 ms
Postgres via RDS Proxy569 ms23 ms
DynamoDB, in a VPC648 ms22 ms
DynamoDB, no VPC623 ms21 ms

The VPC cold-start penalty that shaped a decade of Lambda advice is gone in these numbers. The full report breaks each cold start into initialization, connection and first query, shows what a burst of 200 does to each backend, and what RDS Proxy costs and buys.

Lambda talking to a database?

We'll review your connection handling and cold-start budget with you. 30 minutes, free.

hoolco Monthly Review

Once a month: what changed in tech that month and what it means for you, from cloud and AI to security and the tools you build with. Every item links to its source. No sales pitch, unsubscribe in one click.

As of November 9, 2026. Provided as is, for general information, and accurate to the best of our knowledge on the date shown. Not legal, compliance, tax, financial or other professional advice. Prices, limits and vendor services change; check current vendor documentation before relying on anything here. Terms of use.