.NET has good defaults for running in containers #5485
Labels
area-docker
bulk-closed
Priority:1
Work that is critical for the release, but we could probably ship without
Team:Runtime
User Story
A single user-facing feature. Can be grouped under an epic.
Milestone
People expect that the default behavior of .NET (or any container platform) is good in the general case. To a large degree, the conversation we had in Environment.ProcessorCount incorrect reporting in containers in 3.1 was about that, and we chose to bias default product behavior for the general case.
The assumption at this point is that .NET has good defaults, for the general case. The remaining work is to test this assumption. The following are cases that we will validate (and publish results). Please share if you believe that we should consider more cases, or if you have data to share. These cases are not a list of configurations, but guidance that we can document.
--memory-reservation
) and hard (--memory
) memory limits set, with soft limit n% smaller: 10%, 25%, 50%Note: The tests will be run with API template.
Note: For these cases, only docker, not .NET, settings can be changed. The question is whether we are happy with the results we get, with .NET defaults.
The text was updated successfully, but these errors were encountered: