Document dynamic concurrency limits - #128753
Document dynamic concurrency limits#128753Vladyslav Panasenko (vladyslav-panasenko) wants to merge 1 commit into
Conversation
|
Vladyslav Panasenko (@vladyslav-panasenko) : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change. |
|
Vladyslav Panasenko (@vladyslav-panasenko) : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change. |
|
Learn Build status updates of commit 5bf99f6: ✅ Validation status: passed
For more details, please refer to the build report. |
There was a problem hiding this comment.
Note
Copilot was unable to run its full agentic suite in this review.
Pull request overview
Updates Azure Functions documentation to include the maximumFunctionConcurrency and cpuThreshold settings for dynamic concurrency in both the host.json reference and the dynamic concurrency guide.
Changes:
- Documented
maximumFunctionConcurrencyandcpuThresholdin the host.json reference, including examples and property descriptions. - Expanded the dynamic concurrency guide with a settings table describing key dynamic concurrency knobs.
- Refreshed
ms.datemetadata in both articles.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.
| File | Description |
|---|---|
| articles/azure-functions/functions-host-json.md | Adds maximumFunctionConcurrency/cpuThreshold to sample JSON and the reference table for concurrency settings. |
| articles/azure-functions/functions-concurrency.md | Adds the same settings to the dynamic concurrency sample and introduces a settings summary table. |
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
| | `cpuThreshold` | 0.80 | Sets the CPU usage level at which the host's CPU health throttle can activate. Use a value greater than 0 and less than 1. For example, `0.75` represents 75 percent CPU usage. Lower values cause the host to reduce concurrency at a lower CPU usage level. | | ||
| | `snapshotPersistenceEnabled` | true | Controls whether the host periodically saves learned concurrency values to storage. New instances can start from saved values instead of starting from a concurrency of one and relearning the workload. | | ||
|
|
||
| The host applies `maximumFunctionConcurrency` and `cpuThreshold` only when `dynamicConcurrencyEnabled` is `true`. |
| | dynamicConcurrencyEnabled | false | Enables dynamic concurrency behaviors for all triggers supported by this feature, which is off by default. | | ||
| | maximumFunctionConcurrency | 500 | Sets an upper limit for the concurrency that the host can learn for each function on an instance. The value must be a positive integer, or `-1` to remove the limit. This setting applies only when `dynamicConcurrencyEnabled` is `true`. | | ||
| | cpuThreshold | 0.80 | Sets the CPU usage level at which the host's CPU health throttle can activate. The value must be greater than 0 and less than 1. This setting applies only when `dynamicConcurrencyEnabled` is `true`. | | ||
| | snapshotPersistenceEnabled | true | Learned concurrency values are periodically persisted to storage so new instances start from those values instead of starting from 1 and having to redo the learning. | |
|
Thiago Almeida (@nzthiago) Cary Chai (@cachai2) Can you review the proposed changes? Important: When the changes are ready for publication, adding a #label:"aq-pr-triaged" |
prmerger-automator
Bot
added
the
aq-pr-triaged
Documents maximumFunctionConcurrency and cpuThreshold in the dynamic concurrency guide and host.json reference.
Fixes Azure/azure-functions-host#9295