Memory usage about gateway

[tj]

You're only ever handling one request in a single Lambda container, so even at the low end you have 128mb for a single request—which is usually plenty :D. The only way around that constraint is choosing one of the larger Lambda memory sizes

[mozey]

You're only ever handling one request in a single Lambda container

Ah I thought variables outside the callback passed into lambda.Start might persist across requests depending on how long AWS chooses to keep the container alive.

But if each API Gateway request gets at least 128MB and it's own container, then that's not an issue.

[tj]

What you said is correct actually, you could bloat the memory with a bad caching algorithm or something but in practice I've never exceeded even the 128mb limit