Skip to content
Open
Changes from 4 commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions docs/core/runtime-config/garbage-collector.md
Original file line number Diff line number Diff line change
Expand Up @@ -300,7 +300,7 @@ The following settings apply to all flavors of the GC:

- The heap hard limit is defined as the maximum commit size, in bytes, for the GC heap and GC bookkeeping.
- This setting only applies to 64-bit computers.
- If this limit isn't configured but the process is running in a memory-constrained environment, that is, inside a container with a specified memory limit, a default value is set. That default is the greater of 20 MB or 75% of the memory limit on the container.
- If this limit isn't configured but the process is running in a memory-constrained environment, that is, inside a container with a specified memory limit, a default value is set. That default is the greater of 20 MB or the [heap hard limit percent](#heap-hard-limit-percent) of the memory limit on the container.
Copy link

Copilot AI Dec 3, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The phrase "the heap hard limit percent of the memory limit on the container" is ambiguous. "Heap hard limit percent" is a setting name, not a value, so this phrasing suggests using a setting name in a calculation. Consider: "That default is the greater of 20 MB or the default percentage from Heap hard limit percent (75%) applied to the memory limit on the container." This clarifies that it's using the default percentage value from that setting.

Suggested change
- If this limit isn't configured but the process is running in a memory-constrained environment, that is, inside a container with a specified memory limit, a default value is set. That default is the greater of 20 MB or the [heap hard limit percent](#heap-hard-limit-percent) of the memory limit on the container.
- If this limit isn't configured but the process is running in a memory-constrained environment, that is, inside a container with a specified memory limit, a default value is set. That default is the greater of 20 MB or the default percentage from [Heap hard limit percent](#heap-hard-limit-percent) (75%) applied to the memory limit on the container.

Copilot uses AI. Check for mistakes.
- This setting is ignored if the [Per-object-heap hard limits](#per-object-heap-hard-limits) are configured.

| | Setting name | Values | Version introduced |
Expand Down Expand Up @@ -339,7 +339,7 @@ The following settings apply to all flavors of the GC:

### Heap hard limit percent

- Specifies the heap hard limit as a percentage of the total physical memory. If the process is running in a memory-constrained environment, that is, inside a container with a specified memory limit, the total physical memory is the memory limit; otherwise it's what's available on the machine.
- Specifies the heap hard limit as a percentage of the total physical memory. If the process is running in a memory-constrained environment, that is, inside a container with a specified memory limit, the container limit is considered the total physical memory. If in a memory-constrained environment, the default value is 75%.
Copy link

Copilot AI Dec 3, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The phrase "If in a memory-constrained environment" is a sentence fragment that creates grammatical confusion. The sentence should be rewritten for clarity. Consider: "When in a memory-constrained environment and this setting isn't explicitly configured, the default value is 75%." This provides better flow and clarifies that 75% is the default when the setting is not specified.

Copilot generated this review using guidance from repository custom instructions.
- This setting only applies to 64-bit computers.
- This setting is ignored if the [Per-object-heap hard limits](#per-object-heap-hard-limits) are configured or the [heap hard limit](#heap-hard-limit) is configured.

Expand Down