3 ms·

I'd love to see an honest comparison across other providers, throwing in Google's Firebase Functions and Azure Cloud Functions.

• chrisco255 8y ago
  Here's a good comparison of Lambda vs Azure Functions performance and scaling up to 400 concurrent requests: https://www.azurefromthetrenches.com/azure-functions-vs-aws-lambda-scaling-face-off/ https://www.azurefromthetrenches.com/azure-functions-vs-aws-...
  • doczoidberg 8y ago
    "Since I published this piece Microsoft have made significant improvements to HTTP scaling on Azure Functions and the below is out of date. Please see this post for a revised comparison. https://www.azurefromthetrenches.com/azure-functions-significant-improvements-in-http-trigger-scaling/" https://www.azurefromthetrenches.com/azure-functions-signifi...
    • com2kid 8y ago
      Excellent, though 200ms seems like a long time for a service to respond to something, especially after being warmed up. I'm only so-so happy about GCF's response time. I honestly wonder why these cloud functions take so long to execute after being warmed up.
      • doczoidberg 8y ago
        hmm firebase (google) cloud functions take 2,3s in average for me for a respond (simple json output out of firebase)
        • com2kid 8y ago
          My stupid JSON returning functions average out to around 50ms - 250ms. I'm querying across a couple hundred rows. I'm reasonably certain that calling out to Perl and a regex would be faster for so little data. :/