Collect cold start data for nodeJs worker about azure-functions-nodejs-worker HOT 4 CLOSED

e.g. host.startup.outofproc.nodeworker.latency, host.startup.outofproc.grpcserverstart.latency

from azure-functions-nodejs-worker.

@paulbatum - i've pushed a change that captures "IntializeWorkers" latency and "Grpc server start" latency. Capturing latency for individual language workers (grpc clients) to be running is trickier. The WorkerReady method in LanguageWorkerChannel is when we have received a response from the language worker confirming that it is up and running (ready to receive messages and process functions).

This is trickier because the work is started in the flow of InitializeWorkers, but this call does not block on the worker client being ready. We only know it is ready when we receive an RpcEvent that indicates worker is ready.

How important is capturing this missing data?

from azure-functions-nodejs-worker.

Latency for startProcess method in LanguageWorkerChannel would be good capture to give us an idea on long it takes to start a language worker process. Let’s sync up offline

from azure-functions-nodejs-worker.

Resolved by Azure/azure-functions-host#3270

from azure-functions-nodejs-worker.