Why indexing always go jet turbine engine at 97%?

mike

Logos always go bbrrrrrrrr..... at 97% indexing.

I always wonder, what's the reasoning behind this?

Graham Criddle

At this point, it's actually replacing an index which is intensive in terms of processing power and disk acess.

See extract from indexer.log that demonstrates this - in this case there was a period of about 5 minutes where this activity was taking place

2021-01-21 16:18:01.7294 1 Info WindowsIndexerProgram Setting notification icon tool tip to: Logos Bible Software is indexing (96% complete)
2021-01-21 16:18:12.6329 13 Info SQLite Profile 13.07s in index-build.lxn for: select BucketId, FileOffset from AllBuckets order by BucketId
2021-01-21 16:23:16.8599 1 Info WindowsIndexerProgram Setting notification icon tool tip to: Logos Bible Software is indexing (97% complete)
2021-01-21 16:23:28.9835 13 Info LibraryIndex (5m 34.1s) Building term/document info index
2021-01-21 16:23:28.9845 13 Info LibraryIndex (Timed) Attempting to replace index 'C:\Users\Graham\AppData\Local\Logos5\Data\ijwrwu3e.2ty\LibraryIndex/index' with new index 'C:\Users\Graham\AppData\Local\Logos5\Data\ijwrwu3e.2ty\LibraryIndex/index-build'.
2021-01-21 16:23:28.9915 13 Info FileSystemIndexInfo Replacing C:\Users\Graham\AppData\Local\Logos5\Data\ijwrwu3e.2ty\LibraryIndex/index with C:\Users\Graham\AppData\Local\Logos5\Data\ijwrwu3e.2ty\LibraryIndex/index-build
2021-01-21 16:23:29.5079 13 Info LibraryIndex (523ms) Attempting to replace index 'C:\Users\Graham\AppData\Local\Logos5\Data\ijwrwu3e.2ty\LibraryIndex/index' with new index 'C:\Users\Graham\AppData\Local\Logos5\Data\ijwrwu3e.2ty\LibraryIndex/index-build'.
2021-01-21 16:23:29.5089 13 Info LibraryIndex Library index merge completed in 00:16:41.0984462.