All 19 CLR & Runtime questions
More in CLR & Runtime
What is .NET, and how does it work at a high level? What is the CLR, and why is it central to how .NET applications execute? What is CIL (Common Intermediate Language), and what role does it play between source code and execution? What is the difference between managed and unmanaged code in .NET, and when would you need to work with the latter? How does the CLR's type system distinguish between value types and reference types, and where is each typically allocated? What is the Common Type System (CTS), and how does it enable interoperability between different .NET languages? What is the relationship between the CLR and the .NET class library (BCL - Base Class Library)? What does the `unsafe` keyword and pointer usage in C# allow, and why would a developer opt into it? What is the difference between the CLR's Server GC and Workstation GC modes, and how do you choose between them? What is the AppDomain concept in .NET Framework, and why was it removed from modern .NET?
Advertisement
Back to results for “.NET CLI”
.NET › CLR & Runtime

What is JIT (Just-In-Time) compilation, and how does it differ from ahead-of-time (AOT) compilation?

Intermediate

Answer

JIT compilation translates IL into native machine code at runtime, immediately before a method is first executed, allowing the CLR to optimize compiled code based on the actual runtime environment (CPU architecture, observed usage patterns) -- at the cost of a warm-up delay for the first call to each method. AOT compilation (like Native AOT) instead compiles everything to native code during the publish/build step, eliminating JIT overhead and warm-up time entirely, at the cost of losing some runtime-adaptive optimization opportunities and dynamic code generation capabilities.
// JIT: method compiled to native code the first time it's called
public void ProcessOrder() { ... }  // IL until first invocation, then JIT-compiled

// Native AOT: entire app compiled to native code at publish time
dotnet publish -p:PublishAot=true
Real-world example A CLI tool invoked thousands of times per day (like a git hook) benefits significantly from Native AOT's elimination of JIT warm-up, since JIT's per-invocation startup cost would otherwise dominate the tool's very short total runtime.

Common follow-ups: What is tiered compilation and how does it balance JIT startup cost against optimization?;Why can't Native AOT support all the same runtime reflection scenarios as JIT?

.NET CLI SDK & Project Structure (csproj);Diagnostics & Performance
All 19 CLR & Runtime questions