.NET Core Web API on AWS Lambda Performance

#1

Post by maingi4 » Tue, Feb 14, 2017, 5:03 AM UTC

.NET Core Web API on AWS Lambda Performance
cloudncode.blog

Re: .NET Core Web API on AWS Lambda Performance

#2

Post by LyalinDotCom » Tue, Feb 14, 2017, 7:13 AM UTC

Just worth pointing out that Azure (Microsoft's cloud platform) also has a Serverless option in the form of a cloud platform capability called "Azure Functions". So check out the competitor here: https://azure.microsoft.com/en-us/services/functions

Re: .NET Core Web API on AWS Lambda Performance

#3

Post by nstj » Tue, Feb 14, 2017, 7:33 AM UTC

Nice post!

Would be great if you could post some total latency numbers from client to server and back, as in my experience API Gateway is extremely slow (AWS employees admit as much in their forums). Another problem is that once the Lambda is 'warmed up', if you have scaling needs beyond the 1 container it's allocated then you again have a 'cold start latency' problem. Interested to see whether this had an effect on your setup also (and as a side note, I'm extremely impressed with the potential for Lambda and serverless, but it still doesn't seem ready for prime time IMO).

Re: .NET Core Web API on AWS Lambda Performance

#4

Post by Sacho » Tue, Feb 14, 2017, 7:57 AM UTC

LyalinDotCom wrote: post #2

Just worth pointing out that Azure (Microsoft's cloud platform) also has a Serverless option in the form of a cloud platform capability called "Azure Functions". So check out the competitor here: https://azure.microsoft.com/en-us/services/functions

Thanks! I have been using webjobs for a while and found the experience a bit scattered and subpar(especially the scheduling). Hopefully azure functions are better in this regard.

Re: .NET Core Web API on AWS Lambda Performance

#5

Post by stonewhite » Tue, Feb 14, 2017, 8:51 AM UTC

I wouldn't have deemed it impressive by 'load testing' AWS Lambda with 139 requests.

Also, a simple Google search would have shown the author that first 1 million requests are free in AWS Lambda, contrary to what he says.

Re: .NET Core Web API on AWS Lambda Performance

#6

Post by philliphaydon » Tue, Feb 14, 2017, 11:14 AM UTC

stonewhite wrote: post #5

I wouldn't have deemed it impressive by 'load testing' AWS Lambda with 139 requests. Also, a simple Google search would have shown the author that first 1 million requests are free in AWS Lambda, contrary to what he says.

I don't believe it's 1m... it's 1m depending on the memory configured for the lambda and the total execution time per lambda. If every lambda takes 150ms to run you will only get 500k requests.

Re: .NET Core Web API on AWS Lambda Performance

#7

Post by philliphaydon » Tue, Feb 14, 2017, 11:16 AM UTC

nstj wrote: post #3

Nice post! Would be great if you could post some total latency numbers from client to server and back, as in my experience API Gateway is extremely slow (AWS employees admit as much in their forums). Another problem is that once the Lambda is 'warmed up', if you have scaling needs beyond the 1 container it's allocated then you again have a 'cold start latency' problem. Interested to see whether this had an effect on…

I'm using gateway to proxy requests to IIS, Lambdas, and S3/CloudFront. It's not slow at all for me. It's also nice having a single domain and no longer dealing with CORS.

Re: .NET Core Web API on AWS Lambda Performance

#8

Post by nstj » Tue, Feb 14, 2017, 11:54 AM UTC

philliphaydon wrote: post #7

nstj wrote: post #3

Nice post! Would be great if you could post some total latency numbers from client to server and back, as in my experience API Gateway is extremely slow (AWS employees admit as much in their forums). Another problem is that once the Lambda is 'warmed up', if you have scaling needs beyond the 1 container it's allocated then you again have a 'cold start latency' problem. Interested to see whether this had an effect on…

I'm using gateway to proxy requests to IIS, Lambdas, and S3/CloudFront. It's not slow at all for me. It's also nice having a single domain and no longer dealing with CORS.

Interesting - what's your P95/P99 like? I'm seeing ~800ms with a Hello World Lambda called from API Gateway.

Re: .NET Core Web API on AWS Lambda Performance

#9

Post by nstj » Tue, Feb 14, 2017, 11:57 AM UTC

philliphaydon wrote: post #6

stonewhite wrote: post #5

I wouldn't have deemed it impressive by 'load testing' AWS Lambda with 139 requests. Also, a simple Google search would have shown the author that first 1 million requests are free in AWS Lambda, contrary to what he says.

I don't believe it's 1m... it's 1m depending on the memory configured for the lambda and the total execution time per lambda. If every lambda takes 150ms to run you will only get 500k requests.

It's 1m requests and a compute time space limit

> AWS Lambda is now generally available. The AWS Free Tier includes 1 million free requests and up to 3.2 million seconds of compute time per month with AWS Lambda [0]

[0]: https://aws.amazon.com/lambda/pricing/

Re: .NET Core Web API on AWS Lambda Performance

#10

Post by social_quotient » Tue, Feb 14, 2017, 12:32 PM UTC

stonewhite wrote: post #5

I wouldn't have deemed it impressive by 'load testing' AWS Lambda with 139 requests. Also, a simple Google search would have shown the author that first 1 million requests are free in AWS Lambda, contrary to what he says.

Just a heads up, I think he meant the free tier at load impact.

While I love the service, you do end up paying pretty quick to scale up. https://loadimpact.com/pricing

As a note, we started using GOAD https://goad.io and Dino http://veldstra.org/2016/02/18/project-dino-load-testing-on-... - for running tests and has been great.