Maxing Out CPU

Andrew Hanson

I'm running L5.1a SR-1 on Mac OS 10.8.5 and it is maxing out the CPU (all eight cores). I see no indication that it is indexing. I've closed Logos and reopened it and have the same problem. Any ideas? Is this a known issue?

BillS

On a PC I'd suggest you run task manager & see if Logos indexer is running... If it is, mystery solved, as apparently having multithreading & 4 cores is known to consume ALL 8 virtual cores, at various places in the indexing process. I have Logos indexing in the background now, & following a suggestion I lowered its priority in task manager to BELOW normal. And, for a change, it appears I can still use the touchpad & cursor. (At certain points in the process while indexing, my entire i7 machine has appeared to lock up during indexing--unable even to use the touchpad!). I don't know how to suggest on a Mac that you try the same... perhaps someone else will.

Jack Caviness

https://community.logos.com/discussion/comment/525736#Comment_525736

BillS said:

On a PC I'd suggest you run task manager & see if Logos indexer is running...

The Mac equivalent to task manager is Activity Monitor.

fgh

It's known in the sense that others have reported it (I experienced it yesterday), but not in the sense that they have figured out what is going on.

If you don't already have it, download Logos Logging Utility from the link in Jack's post, install it, and enable logging. Then, if you see  this issue again, and you are indeed not indexing, use the Logging Utility to create a sample and logs, and attach the zip file it gives you to a new post.

Patrick S.

Andrew Hanson said:

I'm running L5.1a SR-1 on Mac OS 10.8.5 and it is maxing out the CPU (all eight cores). I see no indication that it is indexing. I've closed Logos and reopened it and have the same problem. Any ideas? Is this a known issue?

Hi - if you are running a usual desktop Mac then it will be a four core (i5/i7) CPU with hyper-threading which shows as eight cores. I only mention this because Logos, in normal use, will not use all eight cores. Even when indexing, which is usually the most CPU intensive thing it does, it will not use all eight cores.

Therefore if you see your Logos maxing out all eight cores (continuously) then there is definitely something wrong with it. It may be that you have a corrupt resource and/or index. The best thing is to follow the suggestion of fgh and post the log files from your machine — and not use Logos in the meantime as it will not be doing your computer any good to be running the CPU maxed out.

=== UPDATE ===

I stand corrected... Logos must have upgraded the indexer since the last time I investigated (Logos 4 I think). I see now that if it is doing 'light' indexing it doesn't use hyper-threading (first screenshot) but in cases where it does a major book update (I just downloaded the 1,000 book update) with 'major' indexing (like during first installation of Logos) the indexer does use hyper-threading (second screenshot).

Still however if you see all cores (physical + hyper-threading) being maxed out continuously then there is a problem.

Fr. Charles R. Matheny

https://community.logos.com/discussion/comment/525894#Comment_525894

I am having similar issue.

Will be working along just fine and, all of a sudden, logos just slams all processor os well over 100% .

Indexing not running, started the day after last update.

Will not close when this happens, have to force quit.

Bruce Lundquist

https://community.logos.com/discussion/comment/526172#Comment_526172

I'm also having this problem. Here's the situation and analysis.

I have a MacBook Pro Retina with OS 10.8.4. It has 16 GB 1600 MHz DDR3 Memory.
Processor Speed 2.3 CGz with 4 Cores and a Solid State Drive.
Just recently I noticed that this laptop has been running hot and the fan runs a lot.
I found out that the reason is the latest version of Logos 5 is a CPU hog. I'm running Logos 5.1a SR-1 (5.1.1.0600). It's Logos 5 Silver.

Since I'm familiar with Linux (Mac has a Linux kernel) I ran TOP and it shows Logos consuming 218.1% CPU and LogosIndexer using 386.7%. No wonder it's so hot. This is not good for my laptop. Also, exiting Logos doesn't work. It starts Synchronizing which takes a long time. I then exit the Synchronizing screen. This doesn't exit the app however. Because of this I run kill -9 on the PID from a terminal, and it stops immediately and the laptop cools down.

Can this be looked into? This is really a critical problem. I've included a screen shot of TOP, and what ps -ef shows.

bash-3.2$ ps -ef | grep Logos
501 8363 138 0 8:08PM ?? 39:26.01 /Applications/Logos.app/Contents/MacOS/Logos -psn_0_4342820
501 8365 8363 0 8:08PM ?? 84:49.76 /Applications/Logos.app/Contents/MacOS/LogosIndexer.app/Contents/MacOS/LogosIndexer -user 1bl2w8bo.azu -lang en-US

Please help. Thanks and God Bless.

Andrew Hanson

https://community.logos.com/discussion/comment/526246#Comment_526246

Just discovered something. When I'm not online, there's no problem. Could this be a synching issue?

Michael Sullivan

https://community.logos.com/discussion/comment/526172#Comment_526172

Exactly the same here using Mac v5.1a SR-1: works for a while, then slammed at 100%, then have to force quit.  No indexer running.  Sometimes sync arrows are spinning, sometimes not.

BillS

https://community.logos.com/discussion/comment/525736#Comment_525736

BillS said:

On a PC I'd suggest you run task manager & see if Logos indexer is running... If it is, mystery solved, as apparently having multithreading & 4 cores is known to consume ALL 8 virtual cores, at various places in the indexing process. I have Logos indexing in the background now, & following a suggestion I lowered its priority in task manager to BELOW normal. And, for a change, it appears I can still use the touchpad & cursor. (At certain points in the process while indexing, my entire i7 machine has appeared to lock up during indexing--unable even to use the touchpad!). I don't know how to suggest on a Mac that you try the same... perhaps someone else will.

I spoke too soon... it still comes to a place in the indexing process where the DISK is maxed out at 100%. Whenever that happens, the laptop's touchpad (hence the entire laptop, mostly) becomes unresponsive.

I've noticed, too, that at times the whole machine slows down. Since I habitually run with Logos open, I'm going to try closing it to see if that fixes slow response. If that's the case, PC's are also affected & as Elmer Fudd once said, "There's something vewy scwewy going on here!"

BillS

Just saw a Logos response in another thread:
http://community.logos.com/forums/p/68738/526426.aspx#526426