4 ms·
- watchout for latencies (multi-zones apps) time of your lambda functions. - keep your lambda functions warmed up - node has better warmup time than java lamb
by sriram_iyengar 9y ago
- watchout for latencies (multi-zones apps) time of your lambda functions.
- keep your lambda functions warmed up
- node has better warmup time than java lambdas (not sure of python)
- memory size impact of lambda functions (negligible in most cases)
- manage lambda timeouts
- dynamodb latencies are negligible
- api gateway typically does not introduce latencies
- multitenancy challenges with single store of dynamodb
- jedberg 9y ago> node has better warmup time than java lambdas (not sure of python) Python and node are both sub-second, compared to Java's 10+ seconds.
- kagx 9y ago> api gateway typically does not introduce latencies I haven't checked my function thoroughly yet, but I think API gateway introduce quite a bit of latency (at least in my case). My maximum invocation time is 600ms, according to AWS Lambda monitoring tool, but network request takes around 1s (checked in chrome dev tools). Also, worht noting is that my code is hosted in the us-east region and I'm based in Europe. I'm not sure how much latency this introduce.
- sriram_iyengar 9y ago>> Also, worht noting is that my code is hosted in the us-east region and I'm based in Europe. I'm not sure how much latency this introduce. Very much possible, if your regions are different.
- watter 9y agoProbably about 100ms or more on each request (to and from). Slower depending on location and network conditions.
- sriram_iyengar 9y agoYes very much possible if you are requesting across zones. I did extensive testing within zone and couldn't notice anything more than 2-3ms.