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.
2% is a better default as I normally observe apps spent more like 2% in Server GC instead of 5%. I'm still doing some analysis on the effect but for the preview it's better to (hopefully) get data on 2% than 5%. in the local testing with GCPerfSim (only SOH allocations with low surv rate) I'm seeing a small percentage of throughput inc with a bigger percentage of max memory usage. with asp.net benchmarks I'm not seeing nearly as big a difference.
it can be changed via either the
GCDTargetTCP
env var or theSystem.GC.DTargetTCP
runtime config.