Set default large payload offloading threshold to 256 KiB#755
Merged
Conversation
Change the default LargePayloadStorageOptions.ThresholdBytes from 900,000 bytes to 256 KiB (262,144 bytes). Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Contributor
There was a problem hiding this comment.
Pull request overview
Lowers the default large-payload offloading threshold for the Azure Blob Payloads extension so that more serialized payloads are externalized to Azure Blob Storage by default. This is a behavioral change for consumers who enable the feature but do not explicitly set ThresholdBytes.
Changes:
- Updated
LargePayloadStorageOptionsdefaultThresholdBytesfrom 900,000 to 256 KiB (262,144) and refreshed the XML doc accordingly. - Updated the integration test that asserts the default threshold value.
- Added an Unreleased changelog entry describing the new default.
Reviewed changes
Copilot reviewed 3 out of 3 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
| src/Extensions/AzureBlobPayloads/Options/LargePayloadStorageOptions.cs | Changes the default threshold backing field to 256 * 1024 and updates the public XML doc to match. |
| test/Grpc.IntegrationTests/LargePayloadStorageOptionsTests.cs | Updates the default-value assertion/test name to validate the new 256 KiB default. |
| CHANGELOG.md | Documents the default-threshold change under Unreleased. |
YunchuWang
approved these changes
Jul 1, 2026
This was referenced Jul 1, 2026
Merged
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.
Summary
Changes the default large payload externalization (offloading) threshold in
LargePayloadStorageOptions.ThresholdBytesfrom 900,000 bytes to256 KiB (262,144 bytes).
When the Azure Blob Payloads extension is enabled, payloads whose serialized
size is
>= ThresholdBytesare stored out-of-band in Azure Blob Storage insteadof being sent inline. This lowers the default threshold so more payloads are
offloaded by default.
Behavioral change⚠️
This is an intentional behavioral change. Callers who enabled blob payload
offloading without explicitly setting
ThresholdByteswill now externalizepayloads in the 262,144–899,999 byte range that previously stayed inline (adding
blob I/O, a storage dependency, and cost/latency for those payloads). As this is
a preview feature, the default is still subject to change pre-GA.
Migration: to keep the previous behavior, set
ThresholdBytes = 900_000explicitly.