Fixed documentation for MemoryLoadBytes

[mrsharm]

Summary

Fixed documentation for the MemoryLoadBytes section as it was misleading before as it's not a percentage but a quantity with units in bytes.

Fixes an issue in the runtime repo: dotnet/runtime#106712

CC: @Maoni0 @cshung @mangod9 @markples

[dotnet-policy-service]

Tagging subscribers to this area: @dotnet/area-system-runtime

[gewarren]

Thanks for updating this. The wording wasn't exactly clear to me, so I left a suggested change.

[gewarren]

Oops, forgot to change the link in my previous review. We're required to leave off the learn.microsoft.com/locale part of URLs for them to resolve in air-gapped environments.

[Maoni0]

this still reads a bit confusing to me. for example, not sure how the reader would interpret what memory load is a field in the MEMORYSTATUS structure in bytes means and this was the original confusion indicated in dotnet/runtime#94565. I'd suggest we enumerate all cases to make it very clear, something like this -

when a process is not running in a container or running in a container without a memory limit -

• on windows this is (the memory load field of the MEMORYSTATUS structure (which is a percentage) * total physical memory available on the machine).
• on Linux this is the MemAvailable field in /proc/meminfo.
• on FreeBSD...
• ...

when a process is running in a container with a memory limit -

• on Windows...
• ...

also CC-ing @janvorli for review on info about non windows side of things.

[mrsharm]

@janvorli, any feedback here? Explicitly highlighted the source of the memory load calculation, which prior to this change was ambiguously stated. Based on the code of GCToOSInterface::GetMemoryStatus, there were two cases: one with a memory limit set and one without whether in a container or not -- these were basically added to the documentation.

[learn-build-service-prod]

Learn Build status updates of commit 832b8f5:

✅ Validation status: passed

File	Status	Preview URL	Details
xml/System/GCMemoryInfo.xml	✅Succeeded	View

For more details, please refer to the build report.

For any questions, please:

• Try searching the learn.microsoft.com contributor guides
• Post your question in the Learn support channel