New Windows option in 7.9 Beta 1 to make Logos faster

If you can locate the ngen program, you can run it directly rather than using the Logos command line parameter.

A clue to its location can be found in the title bar of the third screenshot of the initial post.

Microsoft documentation for the ngen tool is here: https://docs.microsoft.com/en-us/dotnet/framework/tools/ngen-exe-native-image-generator

You'll want to use the install action.

Assuming the Logos command line parameter simply invokes ngen with the right parameters, someone on the beta program could use task manager or similar to grab the ngen command line that Logos invokes and post that here in the forum. I'm not on the beta program.

Donnie

Other than faster load time with NGen, if I don't often re-open Logos, is there actually a penalty for using NGen, as JIT compiled code is actually faster than NGen once methods are compiled?  I will fiddle with this.

Hi

Got it installed , working with standard stable version.  l am not using  beta version 

It is definitely faster on startup and lightning fast with searches

Is there any particular search test you would like me to do

Mick[:)]

Wrong Logos.exe. Point to the one in Logos\System.

Also. Use the 64 bit version in Framework64 director. 

C:\Windows\Microsoft.NET\Framework64\v4.0.30319\ngen.exe install \Users\Mick\AppData\Local\Logos\System\Logos.exe

hi

Thanks for the info

Still getting an error for the path for some reason

been driving me nuts 

08/08/2017 15:06:28.613 [12228]: Command line: C:\Windows\Microsoft.NET\Framework\v4.0.30319\ngen.exe install \Users\Mick\AppData\Local\Logos\Logos.exe
08/08/2017 15:06:28.633 [12228]: Uninstalling assembly \Users\Mick\AppData\Local\Logos\Logos.exe because of an error during compilation: Failed to load the runtime. (Exception from HRESULT: 0x80131700).
08/08/2017 15:06:28.634 [12228]: Failed to load the runtime. (Exception from HRESULT: 0x80131700)
08/08/2017 15:06:28.634 [12228]: ngen returning 0xffffffff

Also tried the

C:\Windows\Microsoft.NET\Framework64\v4.0.30319\ngen.exe install \Users\Mick\AppData\Local\Logos\System\Logos.exe

This line did bring up the command box

but still giving the same error

The speed is incredible

you wouldn't think they were the same program

thank you for your help

Everything seems stable

mick

Just installed on stable version. So far very pleased with results! [Y]

My laptop automatically updates itself to Windows 10 Creative Update a couple days ago.

After machine and Logos restarted, Logos seemed to went to back to its crawling speed. I didn't know where / how to check whether the NGEN compile was wiped away. I simply reran the NGEN command line and let it compile. Logos is now back to the accelerated speed.

Can you confirm that the Win10 Creative Update would wipe out the NGEN compile, just out of curiosity?

Thanks,

Peter

Yes. Updates to Windows, .NET, or Logos & dependencies can invalidate the compiled assemblies. Rerunning NGEN will update if/only if necessary. (fuslogvw should log failures that indicate an update is required)

What path? It should work if you point to ./Logos/System/Logos.exe

Hi Mark,

Did you find the app to be generally more responsive with ngen? To me, that's the biggest benefit.

Speeding up startup time is nice, but less crucial to me as I keep Logos open all the time, so it only needs to restart during system restart or upgrade installation. Otherwise, it's the click-to-click fast response that makes ngen most valuable to me personally.

Peter

- Searches run faster

- Bible panels (usually with two translations paired up in multiview) initiate faster, and go to new BCV locations faster

- Bible Browser left-side list of filter facets now populates in < 5 seconds (as opposed to spinning for a minute)

- Library window more responsive