-
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 10 replies
-
I think what this chart is telling you is how many threads are active at any particular point in time. I can't see the x-axis, but I assume "minimum" means the minimum thread count over some interval (e.g. 5 minutes). I'm not sure why it would periodically drop to zero - perhaps that could be a glitch that occurs when scaling out. It's very likely that this number includes both threads created in your code and threads created by the functions runtime and any registered trigger listeners.
It depends on what language you're using for your function app. If it's C#/.NET, you can use as many threads as you want. The easiest way to schedule work on new threads is using the If you're using Node.js or Python, your options are more limited in terms of how many threads you can allocate. By default, there is only one thread for the entire app. For Python, you can allocate more threads using the |
Beta Was this translation helpful? Give feedback.
I think what this chart is telling you is how many threads are active at any particular point in time. I can't see the x-axis, but I assume "minimum" means the minimum thread count over some interval (e.g. 5 minutes). I'm not sure why it would periodically drop to zero - perhaps that could be a glitch that occurs when scaling out. It's very likely that this number includes both threads created in your code and threads created by the functions runtime and any registered trigger listeners.
It depends on what language you're using for your function app. If it's C#/.NET, you can use as many threads as you want. The eas…