[Question] [k8s] [Performanjce ]Force Tier1 compilation on start

Open
#110,387 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
csharp, kubernetes
Domain
compilers, devops, performance

Research direction

No file, test, or entry point is named. Start by researching the .NET runtime's JIT and startup compilation behavior in Kubernetes, then determine whether a supported way exists to force Tier1 compilation before serving traffic. Done means providing a documented mechanism or clearly stating the limitation and alternatives.

Written by the indexing model from the issue text.

Description

area-TieredCompilation-coreclr

Hi Guys,

We run a highly loaded app in Kubernetes and we see perf issues after releasing new versions, partially caused by the JIT compilation, we do have probes but it does not help.

Question: How can we force full app tier1 compilation on the startup? Startup duration is not a big deal as we have liveness probes and k8 will use prev version pods while new starts.

Dominant language
C#
Stars
18.3k
Forks
5.6k
PR metrics pending

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from dotnet/runtime

All issues in dotnet/runtime

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.