I just read in an article about JIT Compilation that Java has two modes of operation (client vs. server) which employ different amounts of JIT complation / runtime optimization.
Does .net provide similar modes?
Share
Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I just read in an article about JIT Compilation that Java has two modes of operation (client vs. server) which employ different amounts of JIT complation / runtime optimization.
Does .net provide similar modes?
There are various runtime modes in .NET, but they are mostly related to the garbage collector used. This has a major impact on the runtime, and is especially useful when configuring server programs (and/or highly threading programs where user interaction is lighter).
For details, see the
<gcServer>and<gcConcurrent>configuration options.There are various other configuration options that impact the runtime of the CLR, as well, such as whether to commit the full thread stack, where to look for assemblies, etc – but these are more just “options” rather than major changes in runtime behavior.
However, this does not change the JIT configuration and optimization, which is more platform specific (x86 vs x64, etc) rather than configuration specific.