Speed - Mind Your Collections (Thanks Mark Barnes)

Benjamin Varghese
Benjamin Varghese Member Posts: 149 ✭✭
edited November 2024 in English Forum

I read somewhere from Mark Barnes <not able to find link to that post> that Logos caches collections at startup, and bad collection rules and unnecessary collections can adversely affect performance.

While Logos 8 was way fast for me at startup and on run than Logos 7, I decided to try cleaning up my collections.

I cleaned up all my rules, and deleted unwanted collections, especially the ones where I was doing kind of '*' of everything in a large category like commentaries.

I can see that Logos 8 is way more faster, even on my not-so-top-end 4GB  i5 rotating hard disk laptop,  and wanted to suggest trying this approach to anyone who is affected by sluggishness. 

It was hard to use Logos 7 on my laptop. It used to hog it down. Logos 8 is acceptably fast just like other typical software. Thanks Logos and Mark Barnes.

Tagged:

Comments

  • David Taylor, Jr.
    David Taylor, Jr. Member Posts: 4,380 ✭✭✭

    Good tip, I was not aware of this.

  • Mark Barnes
    Mark Barnes Member Posts: 15,432 ✭✭✭

    I think the thread you saw recently was this one (Anyone else on a go slow?).

    Bad collection rules and unnecessary or very broad visual filters are the two biggest causes of poor Logos performance. If you have clutter in either, and Logos is slow, then it's worth having a cull. (Turning visual filters off isn't sufficient. They run anyway in the background.)

    If you need help in knowing which collections or visual filters are causing the most problems, turn on diagnostic logging and upload a log here or in a new thread (make sure there's a least five minutes worth of logging — and perhaps open your standard layout or Bibles).

    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!

  • Graham Owen
    Graham Owen Member Posts: 254 ✭✭

    Bad collection rules and unnecessary or very broad visual filters are the two biggest causes of poor Logos performance. If you have clutter in either, and Logos is slow, then it's worth having a cull.

    Hi Mark

    So would you say deleting collections when you no longer need them is "good practice"?

    I have a bunch of templates, to save me having to remember how to construct a specific "type" of collection that I use to create the specific one I need. Over time I have collected lots of the specific examples because I did not realise that all of these collections might have a negative impact.

  • Dave Hooton
    Dave Hooton MVP Posts: 36,009

    I have a bunch of templates, to save me having to remember how to construct a specific "type" of collectio

    You should cull these and refer specifically to Mark's thread(s) showing how to use the newer collection rules which are much more efficient.

    Dave
    ===

    Windows 11 & Android 13

  • GaoLu
    GaoLu Member Posts: 3,503 ✭✭✭

    Is there any speed difference between using {} vs "Plus these resources?

  • Mark Barnes
    Mark Barnes Member Posts: 15,432 ✭✭✭

    So would you say deleting collections when you no longer need them is "good practice"?

    Most collections will take just a second or less to run. Very long or complex ones may take as long as 10s on a slow computer.

    It's worth deleting unwanted complex collections, and it's worth culling hundreds of unwanted collections (if you had them), but I personally wouldn't worry if I just had a handful of unwanted simple collections.

    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!

  • Mark Barnes
    Mark Barnes Member Posts: 15,432 ✭✭✭

    GaoLu said:

    Is there any speed difference between using {} vs "Plus these resources?

    No discernible difference.

    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!