undefined | Better HN

0 pointsdoczoidberg7y ago0 comments

"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-signifi...

0 comments

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.

hmm firebase (google) cloud functions take 2,3s in average for me for a respond (simple json output out of firebase)

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. :/

j / k navigate · click thread line to collapse

0 pointsdoczoidberg7y ago0 comments

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.

hmm firebase (google) cloud functions take 2,3s in average for me for a respond (simple json output out of firebase)

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. :/

j / k navigate · click thread line to collapse