Memory, Allocation, and GC Performance
Read allocation evidence, understand generations and object lifetimes, reduce hot-path pressure carefully, and avoid pooling or caching that retains more memory.
Before this lesson
Explain generations and collection pressure
Separate allocation rate from memory leaks
Reduce measured hot-path allocations
The short answer
The .NET garbage collector reclaims unreachable managed objects and optimizes for short-lived allocations. Measure allocation rate, pause impact, and retained memory before changing code; reduce high-volume temporary work without obscuring ownership.
Build the runtime mental model
Managed memory can still leak when live references retain objects longer than intended. Generational collection assumes most objects die young. Large objects follow different compaction behavior, and finalizable objects require extra lifecycle work.
Advanced C# work improves when you separate language syntax, runtime behavior, and application policy. Write down which layer owns the guarantee in this lesson. Then identify the observable evidence—a compiler rejection, test result, generated query, trace, or measurement—that would prove the model correct.
Design the boundary deliberately
Prefer value types for small values with clear copy semantics, but remember boxing and large struct copies. Reuse buffers when ownership is disciplined. Avoid allocating substrings, closures, enumerators, or temporary collections inside a confirmed high-frequency path.
The starter isolates one part of the mental model so it can run in the browser. The exercise moves the same rule into a current local .NET project where packages, framework hosting, diagnostics, and multi-file tests are available.
using System;
struct Coordinate
{
public int X;
public int Y;
}
class Program
{
static void Main()
{
Coordinate point = new Coordinate { X = 3, Y = 4 };
Console.WriteLine(point.X * point.X + point.Y * point.Y);
}
}Expected output
25
Diagnose failure and misuse
Object pooling can retain large graphs and stale state. Caching without eviction is a leak with a friendly name. Forcing GC.Collect usually disrupts the collector’s policy. Lower allocation does not guarantee lower latency.
Classify each failure as a contract violation, transient operational failure, permanent dependency response, concurrency conflict, or programmer defect. That classification determines whether to reject, retry, compensate, cancel, or fail fast. A generic catch-and-continue policy destroys the information needed to make that decision.
| Question | Evidence to inspect | Decision |
|---|---|---|
| Is the input valid? | Validation result and boundary examples | Reject with a stable contract |
| Is the failure transient? | Typed status, exception, and policy context | Retry only when bounded and safe |
| Is state still consistent? | Invariant and transaction outcome | Commit, compensate, or abort |
| Is performance acceptable? | Representative latency and allocation data | Keep simple or optimize one cause |
Apply the concept in production
Use counters, allocation profiles, heap snapshots, and load tests together. Compare retained paths between snapshots and change one source at a time. Keep code clear unless the measured gain matters to service objectives.
Finish by making the result operable. Add structured diagnostics at the boundary, propagate cancellation, avoid sensitive data, and record SDK and dependency versions. Test the public behavior instead of private implementation details. If a framework or provider performs translation, serialization, concurrency, or I/O, include at least one test against the real production technology.
A senior-level review should be able to answer four questions: what contract is promised, who owns lifetime and cleanup, how failures become visible, and what evidence supports the design. If any answer depends on “the framework probably handles it,” inspect the documentation or runtime behavior and turn the assumption into a checked decision.
Quick knowledge check
Answer before you reveal.
01Can managed code have a memory leak?
Yes. Objects remain live when reachable references retain them even if the application no longer needs them.
02What must happen before adding complexity to this design?
State the requirement, preserve a correct baseline, collect evidence, and explain how the proposed mechanism improves a specific quality.
Exercise
Practice challenge
Profile an allocation-heavy parser, identify the dominant temporary objects, implement one focused reduction, and report throughput plus allocated bytes.
Requirements
- The implementation states its contract and ownership boundary explicitly
- Automated checks cover the successful path and at least two meaningful failures
- Diagnostics expose failure context without secrets or swallowed exceptions
- The project documents required SDK, packages, setup, run, and test commands
Optional extension: Measure or load-test the critical path and record whether the evidence justifies another optimization or abstraction.
Open in C# compilerLesson checkpoint
One small step locks it in
Mark this lesson complete, then keep the momentum going.
Clear up the details
Frequently asked questions
When should I use memory, allocation, and gc performance?
Use it when its explicit tradeoff solves a measured requirement or clarifies an owned boundary. Keep the simpler design when the additional mechanism does not improve correctness, operability, or changeability.
Does the browser compiler cover the complete production setup?
No. It runs the focused starter program. Framework, package, database, benchmark, and multi-project work requires a current local .NET SDK and the project commands described in the exercise.
What evidence should I keep after the exercise?
Keep the acceptance cases, automated tests, diagnostic or benchmark output where relevant, and a short decision note describing the chosen boundary and rejected alternative.