Title should be: AWS Lambda still crush all competitors both for response time and throughput
Aren’t response time and throughout directly correlated with one another. If the former drops, the latter will increase, right?
Azure Functions – Significant Improvements in HTTP Trigger Scaling
31–34 of 34 posts
Re: Azure Functions – Significant Improvements in HTTP Trigger Scaling
#32Title should be: AWS Lambda still crush all competitors both for response time and throughput
Aren’t response time and throughout directly correlated with one another. If the former drops, the latter will increase, right?
Nop because the load is supposed to be spread over thousands of servers... Not just one
Re: Azure Functions – Significant Improvements in HTTP Trigger Scaling
#33Is this the Azure equivalent of AWS Lambda? What factors other than some specific affinity to Microsoft makes a company choose Azure over AWS?
Yes it is. What do you mean by Microsoft-specific stuff? I run a bunch of stuff there. When I started using these things their PaaS offerings were much more mature than the AWS counterpart (since they focused more on IaaS).
Examples?
Re: Azure Functions – Significant Improvements in HTTP Trigger Scaling
#34I'm in the middle of trying to move a very simple ETL-light script to Google (want to use bigquery over redshift). The idea was to use Cloud Functions. I have ran into scale problems very fast at Google and now am having to use App Engine and add more complication which I don't have personal engineering skill/capacity. Google support first bumped me up to 12000 max queries per 100 seconds and said that's the limit, b…
According to [1], the standard quota is 1,000,000 invocations per 100 seconds and can be increased. Maybe try asking again for increased quota? If the documentation is incorrect, please file an issue [2]. Counter-intuitively, ending the response before processing the data may actually be hurting your p99 response time. According to [3], instances which are not currently handling a request get very little CPU and gene…
I have paid support. It's socket connections we're hitting super quick.
Interesting and thanks I had no idea on the end response CPU time. It's just storing the json to Google Cloud Storage but it does take 100-300ms it seems!