Speeding up indexing?

Milkman
Milkman Member Posts: 4,880 ✭✭✭
edited November 2024 in English Forum

Am I correct to assume that once indexing has begun it will index faster if you close Logos and let it run without the program open?

mm.

Comments

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

    Milkman said:

    Am I correct to assume that once indexing has begun it will index faster if you close Logos and let it run without the program open?

    It's unlikely to make much difference unless you're really hammering Logos by doing lots of searches, etc. If you're just reading, you can carry on with it open.

    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!

  • Fred Chapman
    Fred Chapman Member Posts: 5,899 ✭✭✭

    Milkman said:

    Am I correct to assume that once indexing has begun it will index faster if you close Logos and let it run without the program open?

    mm.

    i do not have any stats to confirm or deny that, but that is my standard practice because it seems faster

  • Mark Smith
    Mark Smith MVP Posts: 11,822

    Fredc said:

    i do not have any stats to confirm or deny that, but that is my standard practice because it seems faster

    I have to index some resources shortly and will pay attention to the task manager performance. Under L5 my quad core i7 processor only allocated 4 cores to the indexer, so it could theoretically run other programs in the background. Of course, we all know that they run slower while indexing is going on, as does Logos. If the indexer slows Logos down, it might work the other way around, but only if you are actually using Logos extensively as Mark said.

    I'll be interested in seeing how Logos uses the processor and the RAM I have (8 BG) as I index.

    Pastor, North Park Baptist Church

    Bridgeport, CT USA

  • Mark Smith
    Mark Smith MVP Posts: 11,822

    I'll be interested in seeing how Logos uses the processor and the RAM I have (8 BG) as I index.

    While indexing these 56 new volumes my computer never used more then 6GB of RAM, the indexer seemed to be restricted to 4 threads, and CPU usage never rose above about 15%.

    Pastor, North Park Baptist Church

    Bridgeport, CT USA