Skip to content

Using child_process to run code inside a Cloud Function seems to produce significant latency spikes around require statements

License

Notifications You must be signed in to change notification settings

ehacke/cloud-function-latency-spikes

Repository files navigation

cloud-function-latency-spikes

Using child_process to run code inside a Cloud Function seems to produce significant latency spikes around require statements.

Details

Check out this blog post for details and stats.

To Reproduce

  • Clone the repo
  • Run npm install
  • Make sure you have the gcloud SDK installed
  • Run npm run build to build the auto-generated libraries this will use during testing
  • Run npm run deploy:function to push the code as a Cloud Function to your default project
  • Create a .env file in the repo with CLOUD_FUNCTION_URL= whatever the url of the function is that you just created
  • Run npm run run:function to run the test against the function and gather results

About

Using child_process to run code inside a Cloud Function seems to produce significant latency spikes around require statements

Topics

Resources

License

Stars

Watchers

Forks

Releases

No releases published