Update footnotes for payload and connection limits - #128705
Open
Rui Hiraoka (rui-hira) wants to merge 1 commit into
Open
Update footnotes for payload and connection limits#128705Rui Hiraoka (rui-hira) wants to merge 1 commit into
Rui Hiraoka (rui-hira) wants to merge 1 commit into
Conversation
Contributor
|
Rui Hiraoka (@rui-hira) : 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 02b0f37: ✅ Validation status: passed
For more details, please refer to the build report. |
Contributor
|
Can you review the proposed changes? IMPORTANT: When the changes are ready for publication, adding a #label:"aq-pr-triaged" |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
with EEE, we confirmed that Developer and Basic tiers have a smaller effective buffer capacity than Standard and Premium tiers. It would be helpful to document this limitation so customers can properly design, size, and scale their API Management instances for workloads involving large payload buffering.