Enhance documentation on Scalability file uploads and throttling #128077
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Added note about file-upload operations and best practices to avoid throttling.
Contributor
|
@Jesusbar : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change. |
Contributor
|
Learn Build status updates of commit eb2bb98: ✅ Validation status: passed
For more details, please refer to the build report. |
|
|
||
| IoT Central automatically scales its IoT hubs based on the load profiles in your application. IoT Central can scale up individual IoT hubs and scale out the number of IoT hubs in an application. IoT Central also automatically scales other underlying services. | ||
|
|
||
| Note: IoT Central’s auto scale behavior does not consider **file-upload operations**. If your solution relies heavily on file uploads, you may need to manually scale the underlying IoT Hub to avoid throttling, please contact Microsoft support if this is the case. |
Contributor
There was a problem hiding this comment.
Suggested change
| Note: IoT Central’s auto scale behavior does not consider **file-upload operations**. If your solution relies heavily on file uploads, you may need to manually scale the underlying IoT Hub to avoid throttling, please contact Microsoft support if this is the case. | |
| > [!NOTE] | |
| > IoT Central's auto scale behavior does not consider **file-upload operations**. If your solution relies heavily on file uploads, you may need to manually scale the underlying IoT Hub to avoid throttling, please contact Microsoft support if this is the case. |
|
|
||
| Note: IoT Central’s auto scale behavior does not consider **file-upload operations**. If your solution relies heavily on file uploads, you may need to manually scale the underlying IoT Hub to avoid throttling, please contact Microsoft support if this is the case. | ||
|
|
||
| ### Best practices to avoid unexpected throttling for File Upload Scenarios: |
Contributor
There was a problem hiding this comment.
Suggested change
| ### Best practices to avoid unexpected throttling for File Upload Scenarios: | |
| ### Best practices to avoid unexpected throttling for File Upload Scenarios |
Contributor
|
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
Contributor
There was a problem hiding this comment.
Pull request overview
This PR enhances the scalability documentation for IoT Central by adding guidance on file upload operations and throttling prevention. The changes clarify that auto-scaling doesn't account for file uploads and provide actionable best practices.
- Added a note explaining that IoT Central's auto-scaling doesn't cover file-upload operations
- Included best practices for avoiding throttling in file upload scenarios
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
|
|
||
| IoT Central automatically scales its IoT hubs based on the load profiles in your application. IoT Central can scale up individual IoT hubs and scale out the number of IoT hubs in an application. IoT Central also automatically scales other underlying services. | ||
|
|
||
| Note: IoT Central’s auto scale behavior does not consider **file-upload operations**. If your solution relies heavily on file uploads, you may need to manually scale the underlying IoT Hub to avoid throttling, please contact Microsoft support if this is the case. |
There was a problem hiding this comment.
This run-on sentence should be split into two sentences for better readability. Consider breaking after 'throttling' and starting a new sentence with 'Please contact'.
Suggested change
| Note: IoT Central’s auto scale behavior does not consider **file-upload operations**. If your solution relies heavily on file uploads, you may need to manually scale the underlying IoT Hub to avoid throttling, please contact Microsoft support if this is the case. | |
| Note: IoT Central’s auto scale behavior does not consider **file-upload operations**. If your solution relies heavily on file uploads, you may need to manually scale the underlying IoT Hub to avoid throttling. Please contact Microsoft support if this is the case. |
Comment on lines
+113
to
+117
| - Stagger uploads across devices | ||
| - Avoid synchronized uploads (e.g., at top of the hour) | ||
| - Implement client-side exponential backoff on 429 / ThrottleBacklogTimeout | ||
| - Consider alternative ingestion mechanisms (e.g., ADX ingestion, Fabric pipelines, direct storage writes) | ||
| - Test workload behavior under expected production upload patterns |
There was a problem hiding this comment.
The bullet points use inconsistent tab/space characters for indentation. Ensure consistent indentation formatting throughout the list.
Suggested change
| - Stagger uploads across devices | |
| - Avoid synchronized uploads (e.g., at top of the hour) | |
| - Implement client-side exponential backoff on 429 / ThrottleBacklogTimeout | |
| - Consider alternative ingestion mechanisms (e.g., ADX ingestion, Fabric pipelines, direct storage writes) | |
| - Test workload behavior under expected production upload patterns | |
| - Stagger uploads across devices | |
| - Avoid synchronized uploads (e.g., at top of the hour) | |
| - Implement client-side exponential backoff on 429 / ThrottleBacklogTimeout | |
| - Consider alternative ingestion mechanisms (e.g., ADX ingestion, Fabric pipelines, direct storage writes) | |
| - Test workload behavior under expected production upload patterns |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Added note about file-upload operations and best practices to avoid throttling.