Logos 4 A17 indexing time keeps increasing

John Chun
John Chun Member Posts: 15 ✭✭
edited November 2024 in English Forum

Is there any reason why the indexing time keeps increasing? Is there a way to stop it or to find out whether it is still indexing as it should?

John

Comments

  • While indexer running, can open Indexer.log file to watch progress.

    Observation: PC version also has estimation time increasing.

    Keep Smiling [:)]

  • John Chun
    John Chun Member Posts: 15 ✭✭

    Thanks for the advice.

    Now that I have opened the Indexer.log (which I don't know how to read it), what am I suppose look for?

    John

  • Michael Kares
    Michael Kares Member Posts: 506 ✭✭

    should be a thread that says indexed xx out of xx resources x% complete throughout the log file.  The file automatically scrolls as new info is added so if you look at it every minute or so you should see a progress update.

  • John Chun
    John Chun Member Posts: 15 ✭✭

    Thanks Michael. I see a really long list which look something like this "04/18/2010 11:41:06 |  INFO | 10 | MacIndexerProgress | 0.7500 = 0.75 * (1.00 * 0.01 + 1.00 * 0.86 + 1.00 * 0.13 + 0.00 * 0.00) after 2315.0m"

    So according this info, what has gone wrong? I don't think the indexing time should increase over time instead of decrease.

    John

  • Michael Kares
    Michael Kares Member Posts: 506 ✭✭

    The time estimate is based on the size of the resource just indexed so it will fluctuate over time and increase if a large resource has just been indexed.  Somewhere in the mass of the string you just posted should be one similar to what I described earlier.  Unfortunately, i don't have an indexer file on hand to post an example of what I am talking about.

  • John Chun
    John Chun Member Posts: 15 ✭✭

    Thanks Michael. So base on what you said, does it makes sense to wait until indexing to complete? The reason I asked is because I did the same update on another Mac and the indexing took less than an hour to complete (though that Mac is on 8G RAM and this one is on 4G RAM). Something doesn't make sense here...

  • Since several Logos4 tools use indexes (e.g. Passage Guide, Exegetical Guide), allowing indexing to complete is good idea.

    For grins, issued "Rebuild Index" command - took 2 hours 44 minutes overall on 2.8 GHz Quad Core i7 with 8GB RAM to index 212 bible and 1,392 library resources.

    Building BibleIndex took 42 minutes:


    04/18/2010 00:05:36 |  INFO | 4 |      BibleIndex | Library indexing completed in 00:42:03.5906830. 

    04/18/2010 00:05:36 |  INFO | 4 |      BibleIndex | Main index is built; deleting supplemental index. 

    Library Indexing took couple hours - after last library resource indexed, 33 minutes needed to write postings.

    04/18/2010 02:07:20 |  INFO | 26 |    LibraryIndex | Library indexing completed in 02:01:43.9799860. 


    04/18/2010 02:07:20 |  INFO | 26 |    LibraryIndex | Main index is built; deleting supplemental index. 

    LibraryIndex folder usage went from 3.34 GB to 2.6 GB.

    Plan to rebuild index again after A18 released - compare time and error messages.

    Keep Smiling [:)]

  • John Chun
    John Chun Member Posts: 15 ✭✭

    I have resolved the problem by doubling RAM... it only took 30 mins to complete the indexing.