J. Yi

Hi @brunoborges , although there is a strong temptation to write functions depending on variables across invocations, it is against the best-practice of writing serverless code. One suggestion is to...

Worker will use the default `WorkStealingPool` to process requests. So the parallelism level depends on your physical CPU count.

Probably because Azure environment is using a single-processor machine to run your function. The worker need to replace the `WorkStealingPool` with some other thread pool strategy. I will discuss with...

@pragnagopa , not blocking. But we could discuss it offline to choose the most suitable multi-threading strategy.

@pragnagopa , when you decided which threading strategy (now I'm using the thread pool which contains *Physical CPU Count* threads, which may not handle a lot of long running IO-intense...

This requires a detailed planning, and should be at P3 (a nice to have feature). It doesn't block any scenarios by design.