Memory & GC
Reveal answer and reasoning
Dynamic adaptation to application sizes is a CoreCLR policy intended to make heap sizing respond to application characteristics, including long-lived data. Current .NET documentation states that DATAS is enabled by default starting with .NET 9. Treat that as a versioned policy fact, not a universal property of every CLR, historical release or managed runtime. An explicit deployment override and effective runtime version still matter.
Adaptive sizing does not eliminate a memory budget or make poor ownership harmless. A cache that retains every response remains a growing live set. More aggressive memory conservation can trade throughput or collection work against retained capacity. Compare modes with the same input distribution, concurrency, warmup and observation window. A smaller heap in an idle demonstration is not sufficient evidence that a production service meets its latency objective under bursts.
A managed heap hard limit concerns GC heap policy; it is not a cap on every allocation in the process. Native libraries, stacks, runtime metadata, code and other resident memory need space too. The container or operating system can enforce a broader process or group limit. Leave explicit headroom and measure peak combined behavior rather than allocating the entire quota to the managed heap.
Configuration syntax is also part of correctness. Runtime configuration files and environment variables can use different representations for numeric settings. Verify the documented unit and parsing rules for the exact knob rather than copying an unqualified number from an unrelated example. Some settings apply at startup and require a new process. Changing an environment variable in a running application does not establish that the collector adopted a new policy.
What a strong answer covers
- Server GC, background GC and DATAS describe different decisions.
- Managed heap limits leave native and other process memory outside their budget.
- Read effective settings under the real CPU and memory constraints.
Common pitfall
Treating a managed heap limit as a whole-process limit, or assuming a project setting proves the effective runtime mode.
Follow-up questions
- Which startup setting, numeric unit and parsing rule are you verifying?
- How would CPU quota alter the configuration comparison?
Self-review
Choose what to revisit. These marks are your own assessment and are separate from lesson completion.