New Windows option in 7.9 Beta 1 to make Logos faster
Comments
-
I have Logos installed on Drive D (D:\Program Files (86)\Logos\Logos.exe) [I know that is not an 86x] and I got an error message <'D:\Program' is not recognized as an internal or external Command, operable program or batch file.>
GeorgeT
Looks like you might be missing the quotation marks around the path. The system is only reading the path up to the first space.
0 -
I have Logos installed on Drive D (D:\Program Files (86)\Logos\Logos.exe) [I know that is not an 86x] and I got an error message <'D:\Program' is not recognized as an internal or external Command, operable program or batch file.>
GeorgeT
Looks like you might be missing the quotation marks around the path. The system is only reading the path up to the first space.
I got that error once when I accidently mistyped the file path. In my case, I accidently omitted the Logos directory and skipped right to Logos.exe. That got me thinking about the textual criticism and the lives and scribal habits of ancient scribes!
0 -
Randy,
Fantastic tip! I used it and works as advertised. Thanks much!
Glenn Hawkins
0 -
I was able to apply the new performance command. Thanks for the easy instructions.
However, the /ngen command resulted in 40 second startup times, which seemed about the same as before. I used the /unngen command and started getting 12 second startup times. I went back to applying the /ngen command and it slowed down to 40 seconds startup again. I repeated the steps a couple of times and the best results for me are after the /unngen command.
The 12 second startup is much faster than I have ever had before. Any idea why it seems to work faster with the /unngen command?
Either way, I am very happy that I found this. I only spent 15 minutes on this and it will save me over two hours a year, and I will have great joy every time I startup Logos
0 -
I was able to apply the new performance command. Thanks for the easy instructions.
However, the /ngen command resulted in 40 second startup times, which seemed about the same as before. I used the /unngen command and started getting 12 second startup times. I went back to applying the /ngen command and it slowed down to 40 seconds startup again. I repeated the steps a couple of times and the best results for me are after the /unngen command.
The 12 second startup is much faster than I have ever had before. Any idea why it seems to work faster with the /unngen command?
Either way, I am very happy that I found this. I only spent 15 minutes on this and it will save me over two hours a year, and I will have great joy every time I startup Logos
From your description, I'd guess that you ran it with the /ngen command once and noted the startup time. Then you ran it again with the /unngen command and noted the time. However, when you run it with the command, it doesn't actually take effect until the next time you start the application (assuming you give it 30 seconds or so for it to finish up the preparation work it does in the background).
Andrew Batishko | Logos software developer
0 -
Could be. However, I am still getting the faster results 24 hours later. The last command I ran was the /unngen command. Maybe I will try the /ngen command again and wait 24 hours to see what results I get.
Either way, something happened to dramatically improve my start up times.
0
