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

this still reads a bit confusing to me. for example, not sure how the reader would interpret whatmemory load is a field in the MEMORYSTATUS structure in bytes means and this was the original confusion indicated indotnet/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.

@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 ofGCToOSInterface::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 status updates of commit832b8f5:

✅ Validation status: passed

For more details, please refer to thebuild report.

For any questions, please:

• Try searching the learn.microsoft.comcontributor guides
• Post your question in theLearn support channel