New Windows option in 7.9 Beta 1 to make Logos faster
Comments
-
N
Hi
does this only work with the beta only.?
Would like to try with the standard stable version
Mick
0 -
Michael said:
does this only work with the beta only.?
Sorry this is only available with the beta release
0 -
Michael said:
does this only work with the beta only.?
Would like to try with the standard stable version
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.
Andrew Batishko | Logos software developer
0 -
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
0 -
Randy W. Sims said:
You don't need a batch file. Just create a shortcut on your desktop (right-click -> New -> Shortcut) to "%localappdata%\Logos\Logos.exe /ngen" (without parens).
Copy that shortcut, Right-click -> properties and change /ngen to /unngen.
You can also copy these shortcuts to your Logos toolbar.
Great! Thanks. I LOVE this new speed.
0 -
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.
0 -
Just about every aspect of the program is noticeably faster.
I haven't been this excited about the speed of Logos in a long time (since Logos 4).
Peter
0 -
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[:)]
0 -
Hi
I've just checked the log file ngen
This is what I'm getting
08/08/2017 14:43:30.290 [6772]: Command line: C:\Windows\Microsoft.NET\Framework\v4.0.30319\ngen.exe install
\Users\Mick\AppData\Local\Logos\Logos.exe/ngen
08/08/2017 14:43:30.311 [6772]: Uninstalling assembly\Users\Mick\AppData\Local\Logos\Logos.exe/ngen because of an error during compilation: The given assembly name or codebase was invalid. (Exception from HRESULT: 0x80131047).
08/08/2017 14:43:30.312 [6772]: The given assembly name or codebase was invalid. (Exception from HRESULT: 0x80131047)
08/08/2017 14:43:30.312 [6772]: ngen returning 0xffffffffWhat am I doing wrong
mick
0 -
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.exe0 -
Command line should be:
C:\Windows\Microsoft.NET\Framework\v4.0.30319\ngen.exe install
\Users\Mick\AppData\Local\Logos\Logos.exeAndrew Batishko | Logos software developer
0 -
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 0xffffffffAlso tried the
C:\Windows\Microsoft.NET\Framework64\v4.0.30319\ngen.exe install
\Users\Mick\AppData\Local\Logos\System\Logos.exeThis line did bring up the command box
but still giving the same error
0 -
Hi
Got it installed okay now switched off all background applications and Switched off antivirus program
then we ran the command everything is good
thank you for your help
now we'll see how it flies[:)]
2017 15:09:48.531 [8708]: Command line: C:\Windows\Microsoft.NET\Framework64\v4.0.30319\ngen.exe install
\Users\Mick\AppData\Local\Logos\System\Logos.exe/* removed unnecessary lines */
08/08/2017 15:17:09.092 [2592]: ngen returning 0x000000000 -
-
I'm not on the Beta program, but will this work with my Logos Now/latest Logos 7 release?
Also, OK with my aging WIN7 i3 PC?
Perhaps wait for this to be somewhat implemented in an upcoming Logos release?
Thanks for any thoughts!
0 -
Steve Farson said:
I'm not on the Beta program, but will this work with my Logos Now/latest Logos 7 release?
Also, OK with my aging WIN7 i3 PC?
Perhaps wait for this to be somewhat implemented in an upcoming Logos release?
Thanks for any thoughts!
Hi Steve,
This is currently in the Beta cycle for 7.9. Once 7.9 ships to all stable users it will be available to all non-beta users. It should work with your older PC.
0 -
Philana R. Crouch said:
It should work with your older PC.
It seems to depend on the version of .NET. Does Win 7 have the same version as Win 10?
Dave
===Windows 11 & Android 13
0 -
Just installed on stable version. So far very pleased with results! [Y]
0 -
Command line should be:
C:\Windows\Microsoft.NET\Framework\v4.0.30319\ngen.exe install
\Users\Mick\AppData\Local\Logos\Logos.exeFor 64-bit Logos use C:\Windows\Microsoft.NET\Framework64\v4.0.30319\ngen.exe install
\Users\Mick\AppData\Local\Logos\Logos.exeQUESTION:
How do we get rid of previous assemblies as the new one doesn't remove the old one?
Dave
===Windows 11 & Android 13
0 -
Dave Hooton said:
QUESTION:
How do we get rid of previous assemblies as the new one doesn't remove the old one?
Thanks for letting us know. We'll look at ensuring that this gets properly cleaned up. Until then, you should be able to manually clean up the old versions by directly uninstalling by assembly rather than filename. Something like:
C:\Windows\Microsoft.NET\Framework64\v4.0.30319\ngen.exe uninstall Logos
Andrew Batishko | Logos software developer
0 -
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
0 -
PL said:
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)
0 -
Randy W. Sims said:
Rerunning NGEN will update if/only if necessary.
So is it ok to rerun it occasionally just to be sure no updates have knocked the speed back down?
Logos 10 | Dell Inspiron 7373 | Windows 11 Pro 64, i7, 16GB, SSD | iPhone 13 Pro Max
0 -
James Taylor said:
So is it ok to rerun it occasionally
Do it with each update of Logos until the issues raised in this thread have been resolved and this happens automatically.
Dave
===Windows 11 & Android 13
0 -
C:\Windows\Microsoft.NET\Framework64\v4.0.30319\ngen.exe uninstall Logos
It didn't work --> "the specified assembly is not installed". So I'll have to use the filename+full path, as I have two installations of Logos (haven't actually used ngen for the other installation).
EDIT: The uninstall with full path failed --> "the specified assembly is not installed". Possibly because "Note: Starting with the .NET Framework 4, the action
uninstall* is no longer supported."?And installing the other installation (v7.8 SR-1) also failed ---> "Failed to load the runtime" Exception 0x80131700.
Dave
===Windows 11 & Android 13
0 -
What path? It should work if you point to ./Logos/System/Logos.exe
0 -
I excitedly tried this out, but to be honest, I barely notice any improvement. To try and be more scientific, I created a simple layout, and set it to load by default. I then ran Logos three times, and looked at the entry for "StartupUtility Finished startup". I then switched ngen off, and repeated the process.
- With ngen, startup times were 32.96, 34.24 and 32.98. Average is 33.39
- Without ngen, startup times were 35.34, 32.32, and 35.6. Average is 34.32.
So ngen improved performance by 3%, which is well within the margin of error for a test like this.
This is on an Intel i7-3770k with 32Gb RAM, and a Samsung 850 Evo SSD.
This is my personal Faithlife account. On 1 March 2022, I started working for Faithlife, and have a new 'official' user account. Posts on this account shouldn't be taken as official Faithlife views!
0 -
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
0 -
PL said:
Did you find the app to be generally more responsive with ngen?
No, to be honest, although unlike many I've never found Logos particularly slow. Can you give a quick example of something that's much quicker now?
This is my personal Faithlife account. On 1 March 2022, I started working for Faithlife, and have a new 'official' user account. Posts on this account shouldn't be taken as official Faithlife views!
0 -
- 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
0
