Improving API Response Times by Migrating from Cloud Functions to Cloud Run

Re:Improving API Response Times by Migrating from Cloud Func... by obcilion on Tuesday January 11, 2022 @09:00AM (#29891513)

Hi! Author here.

Functions still only run a single request at a time, while Cloud Run can run as many as the container can handle. We want to build for multiple smaller requests, so when we get ~10k requests incoming in a short timespan it's a lot more useful to have Cloud Run.

I may be mistaken, but I believe cold start is roughly the same for both.

[ Parent | on HN ]

Re:Improving API Response Times by Migrating from Cloud Func... by joek1301 on Wednesday January 12, 2022 @06:01PM (#29913978)

Obviously switching away from Cloud Functions does away with the architectural limitation of processing requests serially, but from my (limited) understanding of Node.js internals, Express applications are single-threaded anyway.

Do you have any idea of where your performance gains are coming from? Is there a lot of async, non-blocking waiting happening in the process of fulfilling requests against your API?

[ Parent | on HN ]

Re:Improving API Response Times by Migrating from Cloud Func... by obcilion on Thursday January 13, 2022 @02:27AM (#29917826)

The NodeJS application is single-threaded, but the Node EventLoop can handle a huge amount of parallel requests, especially since most of the time per request is spent waiting for calls to the DB or external APIs.

I believe the majority of our performance gain is from having far fewer cold starts during large traffic loads.

[ Parent | on HN ]

[deleted]

Re:Improving API Response Times by Migrating from Cloud Func... by obcilion on Tuesday January 11, 2022 @09:25AM (#29891738)

Thanks for letting me know :) Definitely not on the same IP, but I sent an email nonetheless.

[ Parent | on HN ]