none
Am I Using RyuJIT? RRS feed

  • Question

  • I've deployed a WCF service to our server. In the web.config, I set the runtime environment to .Net 4.6 like this:

      <startup>
        <supportedRuntime version="v4.0" sku=".NETFramework,Version=v4.6"/>
      </startup>

    This article makes it sound as though RyuJIT will be turned on by default. Is that correct? How do I know if I'm using RyuJIT or not?

    https://github.com/Microsoft/dotnet/blob/master/docs/testing-with-ryujit.md

    Wednesday, October 21, 2015 10:43 PM

Answers

  • Hi MelbourneDeveloper,

    As below article suggested.
    http://stackoverflow.com/questions/31529683/do-i-need-to-target-my-application-to-net-4-6-to-take-advantage-of-ryujit/31534544#31534544
    You should Enable native code debugging option first. Then you could see which version of JIT compiler is used. We can't make a decision from your output log. If you can update your code, you could use below code to make a judgment.
    https://gist.github.com/AndreyAkinshin/0506ad10faf0c2a7b1cb

    Best Regards,
    Li Wang


    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
    Click HERE to participate the survey.

    Friday, October 23, 2015 5:28 AM
    Moderator
  • As far as I can tell you did not enable native code debugging and because of that you only see the loaded managed modules, not the native ones. Or you attached the debugger to an existing process and didn't select the native debugging engine when attaching.

    Another solution is to add the System.Numerics.Vectors NuGet package to your project and then check the value of System.Numerics.Vector.IsHardwareAccelerated. If it's true then you're using RyuJIT as no other .NET Framework JIT compilers have SIMD support.

    Wednesday, October 28, 2015 6:05 AM
    Moderator
  • Thanks Mike. Very helpful. I was able to answer the question in the positive. I had been attaching to process, but I "attached the debugger to an existing process and didn't select the native debugging engine when attaching". I assumed that the debugger would have picked it up because I selected "Automatically determine the type of code to debug".

    After attaching in this way, I was able to see "clrjit.dll" in the list of modules, but there were no other jitters present. So, I am running RyuJIT.

    I did this on my local machine. Now to figure how to test this on our production server (without debugging)...

    Anyway, for now, here are the steps to do this with a debugger:

    • Set your solution to x64
    • For each project:
    • -On the Application tab, set each project to .Net 4.6
    • -On the Debug tab, set "Enable Native code debugging" to true
    • -On the Build tab, ensure that the target platform is x64
    • Deploy, and run your solution, or press play in Visual Studio
    • Attach to the w3wp process, but make sure that you have selected the debugging type as: "Managed (Native compilation)"
    • Go to Debug->Windows->Modules
    • Copy and paste the text from this Window
    • Paste it in to notepad
    • Do a search for "jit"
    • You should see two instances of "clrjit.dll", but no other modules with "jit" in them.

    Note: My application has some non .Net 4.6 dlls in it. Apparently RyuJIT is not too sensitive about this which is one of the reasons I wanted to confirm this.

    Wednesday, October 28, 2015 9:26 PM

All replies

  • Here are the assemblies that are loaded in to W3WP if that helps.

    'w3wp.exe' (CLR v4.0.30319: Domain 6): Unloaded 'C:\WINDOWS\Microsoft.Net\assembly\GAC_64\mscorlib\v4.0_4.0.0.0__b77a5c561934e089\mscorlib.dll'

    'w3wp.exe' (CLR v4.0.30319: /LM/W3SVC/1/ROOT/HelpDesk-5-130899430616139129): Unloaded 'C:\WINDOWS\Microsoft.Net\assembly\GAC_64\System.Web\v4.0_4.0.0.0__b03f5f7f11d50a3a\System.Web.dll'

    'w3wp.exe' (CLR v4.0.30319: /LM/W3SVC/1/ROOT/HelpDesk-5-130899430616139129): Unloaded 'C:\WINDOWS\Microsoft.Net\assembly\GAC_MSIL\System\v4.0_4.0.0.0__b77a5c561934e089\System.dll'

    'w3wp.exe' (CLR v4.0.30319: /LM/W3SVC/1/ROOT/HelpDesk-5-130899430616139129): Unloaded 'C:\WINDOWS\Microsoft.Net\assembly\GAC_MSIL\System.Core\v4.0_4.0.0.0__b77a5c561934e089\System.Core.dll'

    'w3wp.exe' (CLR v4.0.30319: /LM/W3SVC/1/ROOT/HelpDesk-5-130899430616139129): Unloaded 'C:\WINDOWS\Microsoft.Net\assembly\GAC_MSIL\System.Configuration\v4.0_4.0.0.0__b03f5f7f11d50a3a\System.Configuration.dll'

    'w3wp.exe' (CLR v4.0.30319: /LM/W3SVC/1/ROOT/HelpDesk-5-130899430616139129): Unloaded 'C:\WINDOWS\Microsoft.Net\assembly\GAC_MSIL\System.Xml\v4.0_4.0.0.0__b77a5c561934e089\System.Xml.dll'

    'w3wp.exe' (CLR v4.0.30319: /LM/W3SVC/1/ROOT/HelpDesk-5-130899430616139129): Unloaded 'C:\WINDOWS\Microsoft.Net\assembly\GAC_MSIL\System.Web.ApplicationServices\v4.0_4.0.0.0__31bf3856ad364e35\System.Web.ApplicationServices.dll'

    'w3wp.exe' (CLR v4.0.30319: /LM/W3SVC/1/ROOT/HelpDesk-5-130899430616139129): Unloaded 'C:\WINDOWS\Microsoft.Net\assembly\GAC_MSIL\System.Runtime.Caching\v4.0_4.0.0.0__b03f5f7f11d50a3a\System.Runtime.Caching.dll'

    'w3wp.exe' (CLR v4.0.30319: /LM/W3SVC/1/ROOT/HelpDesk-5-130899430616139129): Unloaded 'C:\WINDOWS\Microsoft.Net\assembly\GAC_MSIL\Microsoft.Build.Utilities.v4.0\v4.0_4.0.0.0__b03f5f7f11d50a3a\Microsoft.Build.Utilities.v4.0.dll'

    'w3wp.exe' (CLR v4.0.30319: /LM/W3SVC/1/ROOT/HelpDesk-5-130899430616139129): Unloaded 'C:\WINDOWS\Microsoft.Net\assembly\GAC_MSIL\System.Web.RegularExpressions\v4.0_4.0.0.0__b03f5f7f11d50a3a\System.Web.RegularExpressions.dll'

    'w3wp.exe' (CLR v4.0.30319: /LM/W3SVC/1/ROOT/HelpDesk-5-130899430616139129): Unloaded 'C:\WINDOWS\Microsoft.Net\assembly\GAC_MSIL\System.Drawing\v4.0_4.0.0.0__b03f5f7f11d50a3a\System.Drawing.dll'

    'w3wp.exe' (CLR v4.0.30319: /LM/W3SVC/1/ROOT/HelpDesk-5-130899430616139129): Unloaded 'C:\WINDOWS\Microsoft.Net\assembly\GAC_MSIL\System.Design\v4.0_4.0.0.0__b03f5f7f11d50a3a\System.Design.dll'

    'w3wp.exe' (CLR v4.0.30319: /LM/W3SVC/1/ROOT/HelpDesk-5-130899430616139129): Unloaded 'C:\WINDOWS\Microsoft.Net\assembly\GAC_MSIL\Microsoft.JScript\v4.0_10.0.0.0__b03f5f7f11d50a3a\Microsoft.JScript.dll'

    'w3wp.exe' (CLR v4.0.30319: /LM/W3SVC/1/ROOT/HelpDesk-5-130899430616139129): Unloaded 'C:\WINDOWS\Microsoft.Net\assembly\GAC_MSIL\Microsoft.VisualStudio.Web.PageInspector.Loader\v4.0_1.0.0.0__b03f5f7f11d50a3a\Microsoft.VisualStudio.Web.PageInspector.Loader.dll'

    'w3wp.exe' (CLR v4.0.30319: /LM/W3SVC/1/ROOT/HelpDesk-5-130899430616139129): Unloaded 'C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Temporary ASP.NET Files\helpdesk\9019b5ad\bb97ea47\App_global.asax.kqwymzlm.dll'

    'w3wp.exe' (CLR v4.0.30319: /LM/W3SVC/1/ROOT/HelpDesk-5-130899430616139129): Unloaded 'C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Temporary ASP.NET Files\helpdesk\9019b5ad\bb97ea47\assembly\dl3\36cf8fbf\094cda9c_550cd101\Adapt.Model.Common.dll'

    'w3wp.exe' (CLR v4.0.30319: /LM/W3SVC/1/ROOT/HelpDesk-5-130899430616139129): Unloaded 'C:\WINDOWS\Microsoft.Net\assembly\GAC_MSIL\System.Web.Extensions\v4.0_4.0.0.0__31bf3856ad364e35\System.Web.Extensions.dll'

    'w3wp.exe' (CLR v4.0.30319: /LM/W3SVC/1/ROOT/HelpDesk-5-130899430616139129): Unloaded 'C:\WINDOWS\Microsoft.Net\assembly\GAC_MSIL\System.Web.Services\v4.0_4.0.0.0__b03f5f7f11d50a3a\System.Web.Services.dll'

    'w3wp.exe' (CLR v4.0.30319: /LM/W3SVC/1/ROOT/HelpDesk-5-130899430616139129): Unloaded 'C:\WINDOWS\Microsoft.Net\assembly\GAC_MSIL\System.ServiceModel.Activation\v4.0_4.0.0.0__31bf3856ad364e35\System.ServiceModel.Activation.dll'

    'w3wp.exe' (CLR v4.0.30319: /LM/W3SVC/1/ROOT/HelpDesk-5-130899430616139129): Unloaded 'C:\WINDOWS\Microsoft.Net\assembly\GAC_MSIL\System.ServiceModel.Internals\v4.0_4.0.0.0__31bf3856ad364e35\System.ServiceModel.Internals.dll'

    'w3wp.exe' (CLR v4.0.30319: /LM/W3SVC/1/ROOT/HelpDesk-5-130899430616139129): Unloaded 'C:\WINDOWS\Microsoft.Net\assembly\GAC_MSIL\System.ServiceModel\v4.0_4.0.0.0__b77a5c561934e089\System.ServiceModel.dll'

    'w3wp.exe' (CLR v4.0.30319: /LM/W3SVC/1/ROOT/HelpDesk-5-130899430616139129): Unloaded 'C:\WINDOWS\Microsoft.Net\assembly\GAC_MSIL\SMDiagnostics\v4.0_4.0.0.0__b77a5c561934e089\SMDiagnostics.dll'

    'w3wp.exe' (CLR v4.0.30319: /LM/W3SVC/1/ROOT/HelpDesk-5-130899430616139129): Unloaded 'C:\WINDOWS\Microsoft.Net\assembly\GAC_MSIL\System.IdentityModel\v4.0_4.0.0.0__b77a5c561934e089\System.IdentityModel.dll'

    'w3wp.exe' (CLR v4.0.30319: /LM/W3SVC/1/ROOT/HelpDesk-5-130899430616139129): Unloaded 'C:\WINDOWS\Microsoft.Net\assembly\GAC_MSIL\System.Runtime.Serialization\v4.0_4.0.0.0__b77a5c561934e089\System.Runtime.Serialization.dll'

    'w3wp.exe' (CLR v4.0.30319: /LM/W3SVC/1/ROOT/HelpDesk-5-130899430616139129): Unloaded 'C:\WINDOWS\Microsoft.Net\assembly\GAC_MSIL\System.Net.Http\v4.0_4.0.0.0__b03f5f7f11d50a3a\System.Net.Http.dll'

    'w3wp.exe' (CLR v4.0.30319: /LM/W3SVC/1/ROOT/HelpDesk-5-130899430616139129): Unloaded 'C:\WINDOWS\Microsoft.Net\assembly\GAC_64\System.Transactions\v4.0_4.0.0.0__b77a5c561934e089\System.Transactions.dll'

    'w3wp.exe' (CLR v4.0.30319: /LM/W3SVC/1/ROOT/HelpDesk-5-130899430616139129): Unloaded 'C:\WINDOWS\Microsoft.Net\assembly\GAC_64\System.EnterpriseServices\v4.0_4.0.0.0__b03f5f7f11d50a3a\System.EnterpriseServices.dll'

    'w3wp.exe' (CLR v4.0.30319: /LM/W3SVC/1/ROOT/HelpDesk-5-130899430616139129): Unloaded 'C:\WINDOWS\Microsoft.Net\assembly\GAC_64\System.EnterpriseServices\v4.0_4.0.0.0__b03f5f7f11d50a3a\System.EnterpriseServices.Wrapper.dll'

    'w3wp.exe' (CLR v4.0.30319: /LM/W3SVC/1/ROOT/HelpDesk-5-130899430616139129): Unloaded 'C:\WINDOWS\Microsoft.Net\assembly\GAC_MSIL\System.Xaml.Hosting\v4.0_4.0.0.0__31bf3856ad364e35\System.Xaml.Hosting.dll'

    'w3wp.exe' (CLR v4.0.30319: /LM/W3SVC/1/ROOT/HelpDesk-5-130899430616139129): Unloaded 'C:\WINDOWS\Microsoft.Net\assembly\GAC_MSIL\System.Web.Mobile\v4.0_4.0.0.0__b03f5f7f11d50a3a\System.Web.Mobile.dll'

    'w3wp.exe' (CLR v4.0.30319: /LM/W3SVC/1/ROOT/HelpDesk-5-130899430616139129): Unloaded 'C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Temporary ASP.NET Files\helpdesk\9019b5ad\bb97ea47\App_Web_bbdza2d5.dll'

    'w3wp.exe' (CLR v4.0.30319: /LM/W3SVC/1/ROOT/HelpDesk-5-130899430616139129): Unloaded 'C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Temporary ASP.NET Files\helpdesk\9019b5ad\bb97ea47\assembly\dl3\c4999c9c\f33b58a7_550cd101\Adapt.Presentation.AES.dll'

    'w3wp.exe' (CLR v4.0.30319: /LM/W3SVC/1/ROOT/HelpDesk-5-130899430616139129): Unloaded 'C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Temporary ASP.NET Files\helpdesk\9019b5ad\bb97ea47\App_Web_z2inywu0.dll'

    'w3wp.exe' (CLR v4.0.30319: /LM/W3SVC/1/ROOT/HelpDesk-5-130899430616139129): Unloaded 'C:\WINDOWS\Microsoft.Net\assembly\GAC_MSIL\Microsoft.CSharp\v4.0_4.0.0.0__b03f5f7f11d50a3a\Microsoft.CSharp.dll'

    'w3wp.exe' (CLR v4.0.30319: /LM/W3SVC/1/ROOT/HelpDesk-5-130899430616139129): Unloaded 'C:\WINDOWS\Microsoft.Net\assembly\GAC_64\System.Data\v4.0_4.0.0.0__b77a5c561934e089\System.Data.dll'

    'w3wp.exe' (CLR v4.0.30319: /LM/W3SVC/1/ROOT/HelpDesk-5-130899430616139129): Unloaded 'C:\WINDOWS\Microsoft.Net\assembly\GAC_MSIL\System.ServiceModel.Web\v4.0_4.0.0.0__31bf3856ad364e35\System.ServiceModel.Web.dll'

    'w3wp.exe' (CLR v4.0.30319: /LM/W3SVC/1/ROOT/HelpDesk-5-130899430616139129): Unloaded 'C:\WINDOWS\Microsoft.Net\assembly\GAC_MSIL\System.Activities\v4.0_4.0.0.0__31bf3856ad364e35\System.Activities.dll'

    'w3wp.exe' (CLR v4.0.30319: /LM/W3SVC/1/ROOT/HelpDesk-5-130899430616139129): Unloaded 'C:\WINDOWS\Microsoft.Net\assembly\GAC_MSIL\System.ServiceModel.Activities\v4.0_4.0.0.0__31bf3856ad364e35\System.ServiceModel.Activities.dll'

    'w3wp.exe' (CLR v4.0.30319: /LM/W3SVC/1/ROOT/HelpDesk-5-130899430616139129): Unloaded 'C:\WINDOWS\Microsoft.Net\assembly\GAC_MSIL\System.WorkflowServices\v4.0_4.0.0.0__31bf3856ad364e35\System.WorkflowServices.dll'

    'w3wp.exe' (CLR v4.0.30319: /LM/W3SVC/1/ROOT/HelpDesk-5-130899430616139129): Unloaded 'C:\WINDOWS\Microsoft.Net\assembly\GAC_MSIL\System.Data.DataSetExtensions\v4.0_4.0.0.0__b77a5c561934e089\System.Data.DataSetExtensions.dll'

    'w3wp.exe' (CLR v4.0.30319: /LM/W3SVC/1/ROOT/HelpDesk-5-130899430616139129): Unloaded 'C:\WINDOWS\Microsoft.Net\assembly\GAC_MSIL\System.Xml.Linq\v4.0_4.0.0.0__b77a5c561934e089\System.Xml.Linq.dll'

    'w3wp.exe' (CLR v4.0.30319: /LM/W3SVC/1/ROOT/HelpDesk-5-130899430616139129): Unloaded 'C:\WINDOWS\Microsoft.Net\assembly\GAC_MSIL\System.ComponentModel.DataAnnotations\v4.0_4.0.0.0__31bf3856ad364e35\System.ComponentModel.DataAnnotations.dll'

    'w3wp.exe' (CLR v4.0.30319: /LM/W3SVC/1/ROOT/HelpDesk-5-130899430616139129): Unloaded 'C:\WINDOWS\Microsoft.Net\assembly\GAC_MSIL\System.Web.DynamicData\v4.0_4.0.0.0__31bf3856ad364e35\System.Web.DynamicData.dll'

    'w3wp.exe' (CLR v4.0.30319: /LM/W3SVC/1/ROOT/HelpDesk-5-130899430616139129): Unloaded 'C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Temporary ASP.NET Files\helpdesk\9019b5ad\bb97ea47\assembly\dl3\60d38a86\aee677a1_550cd101\Adapt.Business.AAM.dll'

    'w3wp.exe' (CLR v4.0.30319: /LM/W3SVC/1/ROOT/HelpDesk-5-130899430616139129): Unloaded 'C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Temporary ASP.NET Files\helpdesk\9019b5ad\bb97ea47\assembly\dl3\c73d1343\075b11a0_550cd101\Adapt.Business.AssetInventory.dll'

    'w3wp.exe' (CLR v4.0.30319: /LM/W3SVC/1/ROOT/HelpDesk-5-130899430616139129): Unloaded 'C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Temporary ASP.NET Files\helpdesk\9019b5ad\bb97ea47\assembly\dl3\8ccc13dd\6dc446a1_550cd101\Adapt.Business.AssetValuation.dll'

    'w3wp.exe' (CLR v4.0.30319: /LM/W3SVC/1/ROOT/HelpDesk-5-130899430616139129): Unloaded 'C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Temporary ASP.NET Files\helpdesk\9019b5ad\bb97ea47\assembly\dl3\0cf7ba9d\ed88aaa4_550cd101\Adapt.Business.CodeGeneration.dll'

    'w3wp.exe' (CLR v4.0.30319: /LM/W3SVC/1/ROOT/HelpDesk-5-130899430616139129): Unloaded 'C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Temporary ASP.NET Files\helpdesk\9019b5ad\bb97ea47\assembly\dl3\d12c7eb8\a8e9f3a0_550cd101\Adapt.Business.Common.dll'

    'w3wp.exe' (CLR v4.0.30319: /LM/W3SVC/1/ROOT/HelpDesk-5-130899430616139129): Unloaded 'C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Temporary ASP.NET Files\helpdesk\9019b5ad\bb97ea47\assembly\dl3\67ca0966\5f109ca1_550cd101\Adapt.Business.DataSchema.dll'

    'w3wp.exe' (CLR v4.0.30319: /LM/W3SVC/1/ROOT/HelpDesk-5-130899430616139129): Unloaded 'C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Temporary ASP.NET Files\helpdesk\9019b5ad\bb97ea47\assembly\dl3\a575cc6c\daa991a4_550cd101\Adapt.Business.DataTransformation.dll'

    'w3wp.exe' (CLR v4.0.30319: /LM/W3SVC/1/ROOT/HelpDesk-5-130899430616139129): Unloaded 'C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Temporary ASP.NET Files\helpdesk\9019b5ad\bb97ea47\assembly\dl3\0179fcf5\650faaa0_550cd101\Adapt.Business.RuleHandler.dll'

    'w3wp.exe' (CLR v4.0.30319: /LM/W3SVC/1/ROOT/HelpDesk-5-130899430616139129): Unloaded 'C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Temporary ASP.NET Files\helpdesk\9019b5ad\bb97ea47\assembly\dl3\c76f3a11\2fd94ea0_550cd101\Adapt.Business.Security.dll'

    'w3wp.exe' (CLR v4.0.30319: /LM/W3SVC/1/ROOT/HelpDesk-5-130899430616139129): Unloaded 'C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Temporary ASP.NET Files\helpdesk\9019b5ad\bb97ea47\assembly\dl3\f93927b9\14b03aa4_550cd101\Adapt.Business.ServiceCalls.dll'

    'w3wp.exe' (CLR v4.0.30319: /LM/W3SVC/1/ROOT/HelpDesk-5-130899430616139129): Unloaded 'C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Temporary ASP.NET Files\helpdesk\9019b5ad\bb97ea47\assembly\dl3\04ab5c8b\e7c590a1_550cd101\Adapt.Business.TaskManagement.dll'

    'w3wp.exe' (CLR v4.0.30319: /LM/W3SVC/1/ROOT/HelpDesk-5-130899430616139129): Unloaded 'C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Temporary ASP.NET Files\helpdesk\9019b5ad\bb97ea47\assembly\dl3\2c0d4224\604dc159_b5d8d001\Adapt.Data.AdaptDB.dll'

    'w3wp.exe' (CLR v4.0.30319: /LM/W3SVC/1/ROOT/HelpDesk-5-130899430616139129): Unloaded 'C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Temporary ASP.NET Files\helpdesk\9019b5ad\bb97ea47\assembly\dl3\17bc726e\0e9a33ce_48d9d001\Adapt.Data.AdaptDBWrapper.dll'

    'w3wp.exe' (CLR v4.0.30319: /LM/W3SVC/1/ROOT/HelpDesk-5-130899430616139129): Unloaded 'C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Temporary ASP.NET Files\helpdesk\9019b5ad\bb97ea47\assembly\dl3\ad0c5661\cadcf96a_ff06d101\Adapt.Data.DBF.dll'

    'w3wp.exe' (CLR v4.0.30319: /LM/W3SVC/1/ROOT/HelpDesk-5-130899430616139129): Unloaded 'C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Temporary ASP.NET Files\helpdesk\9019b5ad\bb97ea47\assembly\dl3\59856c1a\ca27c79e_550cd101\Adapt.Data.Generic.dll'

    'w3wp.exe' (CLR v4.0.30319: /LM/W3SVC/1/ROOT/HelpDesk-5-130899430616139129): Unloaded 'C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Temporary ASP.NET Files\helpdesk\9019b5ad\bb97ea47\assembly\dl3\c0f60741\0870cf9f_550cd101\Adapt.Model.AAM.dll'

    'w3wp.exe' (CLR v4.0.30319: /LM/W3SVC/1/ROOT/HelpDesk-5-130899430616139129): Unloaded 'C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Temporary ASP.NET Files\helpdesk\9019b5ad\bb97ea47\assembly\dl3\706f46e4\491490e9_ac0bd101\Adapt.Model.AssetInventory.Custom.dll'

    'w3wp.exe' (CLR v4.0.30319: /LM/W3SVC/1/ROOT/HelpDesk-5-130899430616139129): Unloaded 'C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Temporary ASP.NET Files\helpdesk\9019b5ad\bb97ea47\assembly\dl3\b9c24a21\729ed99e_550cd101\Adapt.Model.AssetInventory.dll'

    'w3wp.exe' (CLR v4.0.30319: /LM/W3SVC/1/ROOT/HelpDesk-5-130899430616139129): Unloaded 'C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Temporary ASP.NET Files\helpdesk\9019b5ad\bb97ea47\assembly\dl3\0b9e6a62\8635439f_550cd101\Adapt.Model.AssetValuation.dll'

    'w3wp.exe' (CLR v4.0.30319: /LM/W3SVC/1/ROOT/HelpDesk-5-130899430616139129): Unloaded 'C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Temporary ASP.NET Files\helpdesk\9019b5ad\bb97ea47\assembly\dl3\ebc64689\4832a69e_550cd101\Adapt.Model.Business.dll'

    'w3wp.exe' (CLR v4.0.30319: /LM/W3SVC/1/ROOT/HelpDesk-5-130899430616139129): Unloaded 'C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Temporary ASP.NET Files\helpdesk\9019b5ad\bb97ea47\assembly\dl3\07e0b4f0\1bed199d_550cd101\Adapt.Model.CodeGeneration.dll'

    'w3wp.exe' (CLR v4.0.30319: /LM/W3SVC/1/ROOT/HelpDesk-5-130899430616139129): Unloaded 'C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Temporary ASP.NET Files\helpdesk\9019b5ad\bb97ea47\assembly\dl3\593dcb14\aba7c69d_550cd101\Adapt.Model.Contacts.dll'

    'w3wp.exe' (CLR v4.0.30319: /LM/W3SVC/1/ROOT/HelpDesk-5-130899430616139129): Unloaded 'C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Temporary ASP.NET Files\helpdesk\9019b5ad\bb97ea47\assembly\dl3\3abc78c7\1d07ade7_ac0bd101\Adapt.Model.Custom.dll'

    'w3wp.exe' (CLR v4.0.30319: /LM/W3SVC/1/ROOT/HelpDesk-5-130899430616139129): Unloaded 'C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Temporary ASP.NET Files\helpdesk\9019b5ad\bb97ea47\assembly\dl3\9d7d75bb\5d3eb79d_550cd101\Adapt.Model.DataSchema.dll'

    'w3wp.exe' (CLR v4.0.30319: /LM/W3SVC/1/ROOT/HelpDesk-5-130899430616139129): Unloaded 'C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Temporary ASP.NET Files\helpdesk\9019b5ad\bb97ea47\assembly\dl3\faf629cf\69e1819e_550cd101\Adapt.Model.DataTransformation.dll'

    'w3wp.exe' (CLR v4.0.30319: /LM/W3SVC/1/ROOT/HelpDesk-5-130899430616139129): Unloaded 'C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Temporary ASP.NET Files\helpdesk\9019b5ad\bb97ea47\assembly\dl3\054627b1\3876af9d_550cd101\Adapt.Model.Documentation.dll'

    'w3wp.exe' (CLR v4.0.30319: /LM/W3SVC/1/ROOT/HelpDesk-5-130899430616139129): Unloaded 'C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Temporary ASP.NET Files\helpdesk\9019b5ad\bb97ea47\assembly\dl3\30214abb\cb60409d_550cd101\Adapt.Model.Financials.dll'

    'w3wp.exe' (CLR v4.0.30319: /LM/W3SVC/1/ROOT/HelpDesk-5-130899430616139129): Unloaded 'C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Temporary ASP.NET Files\helpdesk\9019b5ad\bb97ea47\assembly\dl3\9ac50d59\7ebd559d_550cd101\Adapt.Model.General.dll'

    'w3wp.exe' (CLR v4.0.30319: /LM/W3SVC/1/ROOT/HelpDesk-5-130899430616139129): Unloaded 'C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Temporary ASP.NET Files\helpdesk\9019b5ad\bb97ea47\assembly\dl3\34f5d1b6\199faa9e_550cd101\Adapt.Model.JobScheduling.dll'

    'w3wp.exe' (CLR v4.0.30319: /LM/W3SVC/1/ROOT/HelpDesk-5-130899430616139129): Unloaded 'C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Temporary ASP.NET Files\helpdesk\9019b5ad\bb97ea47\assembly\dl3\8ddb7261\86f640a0_550cd101\Adapt.Model.Presentation.dll'

    'w3wp.exe' (CLR v4.0.30319: /LM/W3SVC/1/ROOT/HelpDesk-5-130899430616139129): Unloaded 'C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Temporary ASP.NET Files\helpdesk\9019b5ad\bb97ea47\assembly\dl3\1e421c61\9767629d_550cd101\Adapt.Model.Security.dll'

    'w3wp.exe' (CLR v4.0.30319: /LM/W3SVC/1/ROOT/HelpDesk-5-130899430616139129): Unloaded 'C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Temporary ASP.NET Files\helpdesk\9019b5ad\bb97ea47\assembly\dl3\2959c000\a346239e_550cd101\Adapt.Model.SystemSetup.dll'

    'w3wp.exe' (CLR v4.0.30319: /LM/W3SVC/1/ROOT/HelpDesk-5-130899430616139129): Unloaded 'C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Temporary ASP.NET Files\helpdesk\9019b5ad\bb97ea47\assembly\dl3\e5a301f8\1ab657ea_ac0bd101\Adapt.Model.TaskManagement.Custom.dll'

    'w3wp.exe' (CLR v4.0.30319: /LM/W3SVC/1/ROOT/HelpDesk-5-130899430616139129): Unloaded 'C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Temporary ASP.NET Files\helpdesk\9019b5ad\bb97ea47\assembly\dl3\4c61a564\69fe539f_550cd101\Adapt.Model.TaskManagement.dll'

    'w3wp.exe' (CLR v4.0.30319: /LM/W3SVC/1/ROOT/HelpDesk-5-130899430616139129): Unloaded 'C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Temporary ASP.NET Files\helpdesk\9019b5ad\bb97ea47\assembly\dl3\1b7d092b\7136a39c_550cd101\Adapt.Utilities.Common.dll'

    'w3wp.exe' (CLR v4.0.30319: /LM/W3SVC/1/ROOT/HelpDesk-5-130899430616139129): Unloaded 'C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Temporary ASP.NET Files\helpdesk\9019b5ad\bb97ea47\assembly\dl3\0e269e5a\2621c69f_550cd101\Adapt.Utilities.Xivic.dll'

    'w3wp.exe' (CLR v4.0.30319: /LM/W3SVC/1/ROOT/HelpDesk-5-130899430616139129): Unloaded 'C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Temporary ASP.NET Files\helpdesk\9019b5ad\bb97ea47\assembly\dl3\e65e9cab\2d15e8a6_550cd101\Adapt.WCF.dll'

    'w3wp.exe' (CLR v4.0.30319: /LM/W3SVC/1/ROOT/HelpDesk-5-130899430616139129): Unloaded 'C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Temporary ASP.NET Files\helpdesk\9019b5ad\bb97ea47\assembly\dl3\3bc65fc3\77914e9d_550cd101\Adapt.WCF.ErrorHandling.dll'

    'w3wp.exe' (CLR v4.0.30319: /LM/W3SVC/1/ROOT/HelpDesk-5-130899430616139129): Unloaded 'C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Temporary ASP.NET Files\helpdesk\9019b5ad\bb97ea47\assembly\dl3\92391454\8c6b0d54_31e5d001\Adapt.WCF.GISReference.dll'

    'w3wp.exe' (CLR v4.0.30319: /LM/W3SVC/1/ROOT/HelpDesk-5-130899430616139129): Unloaded 'C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Temporary ASP.NET Files\helpdesk\9019b5ad\bb97ea47\assembly\dl3\235394a6\eda48c38_46cbd001\Microsoft.Exchange.WebServices.dll'

    'w3wp.exe' (CLR v4.0.30319: /LM/W3SVC/1/ROOT/HelpDesk-5-130899430616139129): Unloaded 'C:\WINDOWS\assembly\GAC_MSIL\Microsoft.ReportViewer.Common\10.0.0.0__b03f5f7f11d50a3a\Microsoft.ReportViewer.Common.dll'

    'w3wp.exe' (CLR v4.0.30319: /LM/W3SVC/1/ROOT/HelpDesk-5-130899430616139129): Unloaded 'C:\WINDOWS\assembly\GAC_MSIL\Microsoft.ReportViewer.WebForms\10.0.0.0__b03f5f7f11d50a3a\Microsoft.ReportViewer.WebForms.dll'

    'w3wp.exe' (CLR v4.0.30319: /LM/W3SVC/1/ROOT/HelpDesk-5-130899430616139129): Unloaded 'C:\WINDOWS\Microsoft.Net\assembly\GAC_MSIL\Microsoft.VisualBasic\v4.0_10.0.0.0__b03f5f7f11d50a3a\Microsoft.VisualBasic.dll'

    'w3wp.exe' (CLR v4.0.30319: /LM/W3SVC/1/ROOT/HelpDesk-5-130899430616139129): Unloaded 'C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Temporary ASP.NET Files\helpdesk\9019b5ad\bb97ea47\assembly\dl3\a0f1ec36\a0795d57_46cbd001\System.Web.Silverlight.dll'

    Wednesday, October 21, 2015 11:21 PM
  • I posted the above because this thread said I could tell by the output window. But, there's not trace of what they said I should be looking for:

    http://stackoverflow.com/questions/22422021/how-do-i-verify-that-ryujit-is-jitting-my-app

    Wednesday, October 21, 2015 11:23 PM
  • Also, this from the modules screen:

     System.Web.ApplicationServices.dll C:\WINDOWS\Microsoft.Net\assembly\GAC_MSIL\System.Web.ApplicationServices\v4.0_4.0.0.0__31bf3856ad364e35\System.Web.ApplicationServices.dll Yes No Skipped loading symbols.  5 4.06.106.0 24/08/2015 2:28 PM 00007FFB27870000-00007FFB2788D000 [11988] w3wp.exe [1] DefaultDomain 
     System.Runtime.Caching.dll C:\WINDOWS\Microsoft.Net\assembly\GAC_MSIL\System.Runtime.Caching\v4.0_4.0.0.0__b03f5f7f11d50a3a\System.Runtime.Caching.dll Yes No Skipped loading symbols.  8 4.06.79.0 1/06/2015 1:41 PM 00007FFB255D0000-00007FFB2561A000 [11988] w3wp.exe [1] DefaultDomain 
     mscorlib.dll C:\WINDOWS\Microsoft.Net\assembly\GAC_64\mscorlib\v4.0_4.0.0.0__b77a5c561934e089\mscorlib.dll Yes No Skipped loading symbols.  1 4.6.106.0 built by: NETFXREL2STAGE 24/08/2015 2:26 PM 00007FFB4C760000-00007FFB4DC29000 [11988] w3wp.exe [1] DefaultDomain 
     System.Web.dll C:\WINDOWS\Microsoft.Net\assembly\GAC_64\System.Web\v4.0_4.0.0.0__b03f5f7f11d50a3a\System.Web.dll Yes No Skipped loading symbols.  2 4.6.106.0 built by: NETFXREL2STAGE 24/08/2015 2:34 PM 00007FFB2D190000-00007FFB2E137000 [11988] w3wp.exe [1] DefaultDomain 
     System.dll C:\WINDOWS\Microsoft.Net\assembly\GAC_MSIL\System\v4.0_4.0.0.0__b77a5c561934e089\System.dll Yes No Skipped loading symbols.  3 4.6.79.0 built by: NETFXREL2 1/06/2015 1:41 PM 00007FFB4AE70000-00007FFB4BA83000 [11988] w3wp.exe [1] DefaultDomain 
     System.Core.dll C:\WINDOWS\Microsoft.Net\assembly\GAC_MSIL\System.Core\v4.0_4.0.0.0__b77a5c561934e089\System.Core.dll Yes No Skipped loading symbols.  4 4.6.79.0 built by: NETFXREL2 1/06/2015 1:41 PM 00007FFB48A30000-00007FFB493B2000 [11988] w3wp.exe [1] DefaultDomain 
     System.Configuration.dll C:\WINDOWS\Microsoft.Net\assembly\GAC_MSIL\System.Configuration\v4.0_4.0.0.0__b03f5f7f11d50a3a\System.Configuration.dll Yes No Skipped loading symbols.  6 4.6.79.0 built by: NETFXREL2 1/06/2015 1:41 PM 00007FFB482B0000-00007FFB483D0000 [11988] w3wp.exe [1] DefaultDomain 
     System.Xml.dll C:\WINDOWS\Microsoft.Net\assembly\GAC_MSIL\System.Xml\v4.0_4.0.0.0__b77a5c561934e089\System.Xml.dll Yes No Skipped loading symbols.  7 4.6.79.0 built by: NETFXREL2 1/06/2015 1:41 PM 00007FFB47A10000-00007FFB482AB000 [11988] w3wp.exe [1] DefaultDomain 
     Microsoft.Build.Utilities.v4.0.dll C:\WINDOWS\Microsoft.Net\assembly\GAC_MSIL\Microsoft.Build.Utilities.v4.0\v4.0_4.0.0.0__b03f5f7f11d50a3a\Microsoft.Build.Utilities.v4.0.dll Yes No Skipped loading symbols.  9 4.6.79.0 built by: NETFXREL2 1/06/2015 1:45 PM 00007FFB25270000-00007FFB25374000 [11988] w3wp.exe [1] DefaultDomain 
     System.Web.RegularExpressions.dll C:\WINDOWS\Microsoft.Net\assembly\GAC_MSIL\System.Web.RegularExpressions\v4.0_4.0.0.0__b03f5f7f11d50a3a\System.Web.RegularExpressions.dll Yes No Skipped loading symbols.  10 4.6.79.0 built by: NETFXREL2 1/06/2015 1:40 PM 00007FFB3FE70000-00007FFB3FEBC000 [11988] w3wp.exe [1] DefaultDomain 
     System.Design.dll C:\WINDOWS\Microsoft.Net\assembly\GAC_MSIL\System.Design\v4.0_4.0.0.0__b03f5f7f11d50a3a\System.Design.dll Yes No Skipped loading symbols.  12 4.6.79.0 built by: NETFXREL2 1/06/2015 1:40 PM 00007FFB1E220000-00007FFB1EE2E000 [11988] w3wp.exe [1] DefaultDomain 
     System.Drawing.dll C:\WINDOWS\Microsoft.Net\assembly\GAC_MSIL\System.Drawing\v4.0_4.0.0.0__b03f5f7f11d50a3a\System.Drawing.dll Yes No Skipped loading symbols.  11 4.6.93.0 built by: NETFXREL2STAGE 16/07/2015 2:42 PM 00007FFB2F700000-00007FFB2F8EA000 [11988] w3wp.exe [1] DefaultDomain 

    Wednesday, October 21, 2015 11:23 PM
  • Hi MelbourneDeveloper,

    Thank you for posting in MSDN forum

    This forum is discuss .NET Framework Setup and Servicing

     As your issue is related to CLR, I help you move this case to Class library forum for dedicated support.

    Thank you for your understanding.

    Best Regards,

    Wen Xu


    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.

    Click HERE to participate the survey.


    • Edited by 宝宝徐 Thursday, October 22, 2015 8:44 AM
    Thursday, October 22, 2015 8:40 AM
  • Why did you move it here? This clearly IS a question about ".NET Framework Setup and Servicing ". This is a question from the point of view of someone configuring a .Net application installed in IIS. The question is which JIT the framework will be using. This question has nothing to do with the.NET Framework Base Classes as the section you have moved it to. Please move it back, or find a more appropriate place to put this question.

    Thursday, October 22, 2015 9:39 PM
  • Hello MelbourneDeveloper,

    The .NET Setup and Servicing forum is about "install/uninstall .NET Framework". So if you have any questions about install/uninstall .NET Framework, that is the right forum.

    But if you have any questions about configure and use .NET Framework in your environment. That is out of the .NET Setup forum scope.

    I checked your question, sounds like you want to configure the setting by set the startup node and expect the RyuJIT to be enabled by default. This is more related to the useage/configuration problem of .NET Framework.

    Best regards,

    Barry


    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
    Click HERE to participate the survey.

    Friday, October 23, 2015 3:23 AM
  • Fine. Could you please move my post to the appropriate forum then?
    Friday, October 23, 2015 5:24 AM
  • Hi MelbourneDeveloper,

    As below article suggested.
    http://stackoverflow.com/questions/31529683/do-i-need-to-target-my-application-to-net-4-6-to-take-advantage-of-ryujit/31534544#31534544
    You should Enable native code debugging option first. Then you could see which version of JIT compiler is used. We can't make a decision from your output log. If you can update your code, you could use below code to make a judgment.
    https://gist.github.com/AndreyAkinshin/0506ad10faf0c2a7b1cb

    Best Regards,
    Li Wang


    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
    Click HERE to participate the survey.

    Friday, October 23, 2015 5:28 AM
    Moderator
  • I've already followed the instructions from that post. I posted the results at the top of the thread. The post says "If you see compatjit.dll back then you are using the legacy jitter. Do note that you'll always see clrjit.dll", but after searching through the loaded modules, I can't either of these.

    Again, how do we confirm which jit is being used?

    Tuesday, October 27, 2015 9:36 PM
  • Hi MelbourneDeveloper,

    >>but after searching through the loaded modules, I can't either of these.

    Did you enable native code debugging option at properties window of your project?

    >>how do we confirm which jit is being used?

    A simple rule is if your application run on .NET Framework 4.6, RyuJIT is used as default.

    Best Regards,
    Li Wang


    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
    Click HERE to participate the survey.

    Wednesday, October 28, 2015 3:04 AM
    Moderator
  • Yes.

    Well, how can I find out for sure?

    Wednesday, October 28, 2015 3:05 AM
  • As far as I can tell you did not enable native code debugging and because of that you only see the loaded managed modules, not the native ones. Or you attached the debugger to an existing process and didn't select the native debugging engine when attaching.

    Another solution is to add the System.Numerics.Vectors NuGet package to your project and then check the value of System.Numerics.Vector.IsHardwareAccelerated. If it's true then you're using RyuJIT as no other .NET Framework JIT compilers have SIMD support.

    Wednesday, October 28, 2015 6:05 AM
    Moderator
  • Thanks Mike. Very helpful. I was able to answer the question in the positive. I had been attaching to process, but I "attached the debugger to an existing process and didn't select the native debugging engine when attaching". I assumed that the debugger would have picked it up because I selected "Automatically determine the type of code to debug".

    After attaching in this way, I was able to see "clrjit.dll" in the list of modules, but there were no other jitters present. So, I am running RyuJIT.

    I did this on my local machine. Now to figure how to test this on our production server (without debugging)...

    Anyway, for now, here are the steps to do this with a debugger:

    • Set your solution to x64
    • For each project:
    • -On the Application tab, set each project to .Net 4.6
    • -On the Debug tab, set "Enable Native code debugging" to true
    • -On the Build tab, ensure that the target platform is x64
    • Deploy, and run your solution, or press play in Visual Studio
    • Attach to the w3wp process, but make sure that you have selected the debugging type as: "Managed (Native compilation)"
    • Go to Debug->Windows->Modules
    • Copy and paste the text from this Window
    • Paste it in to notepad
    • Do a search for "jit"
    • You should see two instances of "clrjit.dll", but no other modules with "jit" in them.

    Note: My application has some non .Net 4.6 dlls in it. Apparently RyuJIT is not too sensitive about this which is one of the reasons I wanted to confirm this.

    Wednesday, October 28, 2015 9:26 PM