Optimizing Logos 7 for Speed?

Recently, I sat down with a friend who is new to Logos Bible Software. He wanted me to show him around the software so he could get moving in the right direction. We have the same computer (Macbook Pro; 2.2GHz quad-core Intel Core i7; 16GB of 1600MHz DDR3L RAM; 256GB PCIe-based SSD) and the same version of the software. I have about 10 years of use (i.e. documents, visual filters, collections, etc.) and roughly 10,000 more resources. So, when I noticed how fast he was able to move around the software mirroring my machine while it was struggling to perform basic functions (i.e. opening context menu, sympathetic highlighting, etc.).

This got me thinking about possible tips to optimize Logos 7 for speed. I know it has been mentioned on the forums elsewhere that limiting the number of collections can help with speed. What other tips do you have to optimize Logos 7 for speed?

Find more posts tagged with

Comments

(‾◡◝)

For Windows (Sorry. I don't believe there is a Mac equivalent): Set use Ngen to Yes

See here for one of the discussions on this topic. Note that this must be rerun every time an update is installed so it is easiest if you create an link/icon. It is a noticeable speed improvement.

Jack Hairston

This got me thinking about possible tips to optimize Logos 7 for speed. I know it has been mentioned on the forums elsewhere that limiting the number of collections can help with speed. What other tips do you have to optimize Logos 7 for speed?

Your friend has a large advantage in that there's not much data saved on his system (Notes, Layouts, etc.) By planning ahead, he can keep Logos running fast. Here are tips I use to maintain speedy response. It also allows me to get going on a study in seconds.

8345.Logos Speed Tips.docx

JC54

https://community.logos.com/discussion/comment/959080#Comment_959080

about the third speed tip, can you without risks remove the web cache en fasten up your Logos?

Jack Hairston

https://community.logos.com/discussion/comment/959091#Comment_959091

about the third speed tip, can you without risks remove the web cache en fasten up your Logos?

Good question, but I don't know the answer. Perhaps an Internet guru will chime in.

John Kight

Thanks for the tips. I started to migrate all my notes outside of Logos a while back (not including highlights, which I do minimally). I also removed many of my collections as well. I'm still feeling like I'm in a speed trap. My hardware should be more than capable of handling Logos 7.

JT (alabama24)

https://community.logos.com/discussion/comment/959135#Comment_959135

Logs would help a techie decipher your bottlenecks.

Pieter J.

MSi GP72 6QE Win 10 Pro x64 -based Intel(R) Core(TM) i7-6700HQ CPU @ 2.60GHz, 2601 Mhz, 4 Core(s) , 8 Logical Processor(s) GPT 128GB SSD (don't know read and write speeds) with 8GB DDR4 RAM with Intel HD Graphics 530 & NVIDIA GeForce GTX 950M graphics processors.

1) On this laptop it's possible to select the graphics processor to use for Logos. There is a noticable performance increase in some areas when using the NVIDIA processor.

2) A Bible with no Visual Filters turned on and show inline search turned off take 1.5 sec to open. If Show Inline Search is on it drops to 3-4 sec.

3) Other running processes can also drop performance. I use AutoHotkey to map some keyboard keys. The script also make use of HotKeys if Logos is active. When I close this script there is also a performance increase. I don't know why, but I'm almost certain that closing dropbox also made a difference, but I can't verify this.

4) "Set use Internet to No" has a minor impact on startup, but it is sometimes noticable.

5) The WebChache on this system is 0.98GB. Removing it made no difference. I suppose it will as soon as I try to use anything related to the chached items.

6) I did not see a difference between "set use ngen to no" and "set use ngen to yes" except for the time a search may take. But it's to small to notice on this setup.

7) When running on battery power some HD disk speeds drops from lets say 7200rpm to 5200rpm slowing down any process reading or writing to the disk.

John Kight

https://community.logos.com/discussion/comment/959146#Comment_959146

Logs would help a techie decipher your bottlenecks.

I'll post logs tonight when I get home from work. Thanks for the help!

John Goodman

https://community.logos.com/discussion/comment/959155#Comment_959155

On a mac you'll probably find the best speed boost from turning off notes and visual filters. Linked sets can be an issue too. If you use the info panel then you can make that respond to clicking rather than hovering and also customize what is shown down to what you want to see...

(‾◡◝)

https://community.logos.com/discussion/comment/959223#Comment_959223

Don't forget the Optimizing Logos Performance article in the Logos.com support pages (it's the same info for Windows and Mac).

FrMoses

https://community.logos.com/discussion/comment/959239#Comment_959239

Personally, I hope the Logos app will be further enhanced to take advantage of multi core processors and the increasingly large amounts of memory that ship with today’s Macs and PCs. On my 8-core Mac Pro with 64 GB (a video editing machine), Logos barely uses the available resources. It would be nice to see the CPU and memory loads increase!

Don Awalt

https://community.logos.com/discussion/comment/961246#Comment_961246

I have a very fast 2017 MBP with a large library, and it was getting slower and slower. I deleted all my visual filters and don't use the feature any more except temporarily (it's been awhile but I seem to recall that there were still startup delays due to visual filters even if they are turned off), clippings were moved to another product, and I removed all prayer lists since they are stored unencrypted on FL servers.

Now my system moves pretty quickly! It seems to me Bob acknowledged in the whole FL Essentials discussion that continually adding new features was not a good strategy, and I share your hope that some serious improvement in performance is coming. It would be nice if all supported features were truly usable without unreasonable penalties.