Logos 6 constantly indexing

Ever since I installed Logos 6 (Silver) on my new Surface Pro 4 it is indexing....and indexing.....and indexing. And it is continuously using 90%+ of CPU - on a Core i7 no less.

Is there any way to disable it permanently? I tire of using CTRL+ALT+DEL to kill it after every session in Logos and my experience is that the potential benefits are not worth listening to my fan on all the time simply because the indexer is improperly written (any process using 90+% of CPU on a Core i7 is improperly written).

Find more posts tagged with

Comments

MJ. Smith

Have you ever permitted it to complete once? It will keep trying until indexing completes because many features are dependent upon the indexes. Is the percentage complete going up or is it "stuck"? If stuck we will need logs to see where the problem lies - likely a corrupt resource.

Dave Hooton

Is there any way to disable it permanently?

You won't be able to search your resources nor perform certain other functions until indexing is complete, so it cannot be disabled.

(any process using 90+% of CPU on a Core i7 is improperly written).

90% usage isn't unusual during indexing and some recent i7's have only two cores running four threads; usually found on tablets because of their low heat requirement.

I would expect indexing to take 1.5 to 2.5 hours for Logos Silver, so if it does not complete we need to see some logs to diagnose the problem.

Joel Tamburo

https://community.logos.com/discussion/comment/791025#Comment_791025

Hi!

I finally kill it after about 3 hours typically. Remember this device has a Core i7 with four threads plus it uses an NVMe PCIe SSD so the I/O access is superfast. With this sort of hardware the indexing should not be taking anything like this long or taking 90+% of CPU.

The reason I wind up wondering about the indexing is because I run FAR more demanding software on this device and it never pushes the CPU up over 90% despite doing things like intensive database writes. The fact that this does implies something is wrong - either the corrupted resource or the indexing process is not properly distributing its load across threads.

I hate to think what would happen with a Core M or Atom - the device would probably grind to a halt.

NB.Mick

https://community.logos.com/discussion/comment/791026#Comment_791026

I finally kill it after about 3 hours typically.

You can either let it run (e.g. overnight) until it - hopefully - finishes or post some logs allowing us to see if something unusual/broken is happening.

JT (alabama24)

https://community.logos.com/discussion/comment/791026#Comment_791026

How full is the drive?

Joel Tamburo

https://community.logos.com/discussion/comment/791061#Comment_791061

The drive is virtually empty.

UPDATE: I let it run all night and after 7 hours it finished. I am going to launch Logos and see if it starts indexing again.