Re:Ask HN: How was your experience with AWS Lambda in produc...
by Prefinem on Monday June 26, 2017 @06:42PM
(#14641029)
Just a follow up, after the issue last week with AWS Lambda in East-1 (thursday I believe) VPC is not longer causing any additional overhead.
I am not sure what happened, but I had to move a couple of functions inside the VPC and our response times have remained the same.
Re:Ask HN: How was your experience with AWS Lambda in produc...
by Prefinem on Thursday June 22, 2017 @10:30AM
(#14612464)
Just hit one of our test endpoints
Test #1 Lambda run time (140 ms) Total waiting time (354ms) Total time (358ms)
Test #2 Lambda run time (300 ms) Total waiting time (490ms) Total time (567ms)
Test #3 Lambda run time (139 ms) Total waiting time (479ms) Total time (485ms)
This is for a 20kb payload single request.
Stack: Custom Domain -> Cloudfront -> API Gateway -> VPC -> Lambda -> NAT Gateway -> ElasticSearch
Re:Ask HN: How was your experience with AWS Lambda in produc...
by digitalsanctum on Friday June 23, 2017 @11:02AM
(#14619662)
I'm curious why you have a NAT gateway between your Lambda and Elasticsearch?
I haven't tried with a NAT Gateway.
This is what I know.
If the response is small, the request duration is small.
Cloudfront > Gateway > Lambda > RDS (PostgreSQL)
Response:
1k | 20ms-60ms
10k | 50ms-90ms
100k | 150ms-200ms
350k | 200ms-450ms
That's a rough gauge of what I've experienced.
I think the throughput on the gateway is the bottleneck.