Bug 7.8 Beta 2: Indexing Interaction & Excess CPU

When Beta 2 had been downloaded I got a restart message + resource updates awaiting restart. On restart, the indexing message appeared and has not gone away (changing Search types does not affect it). The download processed was for DB:PREACHINGTHEMES and the indexer did not start (not required?). Other resources were indexed by Beta 1 a few minutes before Setup for Beta 2.

Beta 2 has been using 28% - 30% CPU since processing DB:PREACHINGTHEMES. This continues after Closing All Panels. 2 x CEF processes are active @ 0.3% max, with the other @ 0% CPU.

Sync errors continue after my internet service was resumed (there were a couple of outages).

0160.Indexer warn.zip

After a (normal) restart to the previous blank layout the Indexer is started and Logos CPU resumes at 27% after a minute or so (probably after the Indexer finished). There is no warning message in the Search panel and Sync is OK. There are no CEF processes as I haven't accessed Home Page.

3223.LogosCPU.zip

EDIT: After a further restart my normal layout loaded very quickly! But the excess CPU continues as the sole issue.

2211.LogosCPU-2.zip

EDIT 2: The CPU ramps up to 56% when I'm in my other User account. Logos was not running in this account throughout all these issues, and when started it did not impact the CPU used by Beta 2.

Find more posts tagged with

Comments

Bradley Grainger (Logos)

If this happens consistently for you, please capture a sample with "start profiling". Full instructions here: https://wiki.logos.com/Logos_Windows_Profiler_Utility

Tim Hensler

Hi Bradley,

Sorry I don't have time to test and document using the profiler utility at this time, but I have noticed that ever since the 7.8 Beta 2 update, the fan on my laptop runs much faster and my battery lasts about 50% less with 7.8 Beta 2 than it did with Beta 1. Also, Logos at times seems to run slower, especially when filling in a right-click menu or other look-up/search intensive function. I've restarted Logos 3+ times since the update and every time I start Logos my fan speed increases within a minute and continues to run at above normal until I exit Logos. When I close Logos, my fan speed drops to a normal level within 15 seconds. This is a consistent problem every time I use Logos, which has now been over 6 times since the update.

Philana R. Crouch

When Beta 2 had been downloaded I got a restart message + resource updates awaiting restart. On restart, the indexing message appeared and has not gone away (changing Search types does not affect it). The download processed was for DB:PREACHINGTHEMES and the indexer did not start (not required?). Other resources were indexed by Beta 1 a few minutes before Setup for Beta 2.

Beta 2 has been using 28% - 30% CPU since processing DB:PREACHINGTHEMES. This continues after Closing All Panels. 2 x CEF processes are active @ 0.3% max, with the other @ 0% CPU.

Sync errors continue after my internet service was resumed (there were a couple of outages).

0160.Indexer warn.zip

After a (normal) restart to the previous blank layout the Indexer is started and Logos CPU resumes at 27% after a minute or so (probably after the Indexer finished). There is no warning message in the Search panel and Sync is OK. There are no CEF processes as I haven't accessed Home Page.

3223.LogosCPU.zip

EDIT: After a further restart my normal layout loaded very quickly! But the excess CPU continues as the sole issue.

2211.LogosCPU-2.zip

EDIT 2: The CPU ramps up to 56% when I'm in my other User account. Logos was not running in this account throughout all these issues, and when started it did not impact the CPU used by Beta 2.

Dave,

Just to clarify, after indexing has completed does your CPU stay at a high rate? Are there any specific things you are doing in the app? Grabbing a process sample will be very helpful.

Dave Hooton

Grabbing a process sample will be very helpful.

Already done & email sent to testing:-

"Started Logos with a blank layout and began profiling ASAP. CPU use was 30% - 32% throughout (26% - 28% without the profiler).

No downloads, syncing normally. No user inputs/use."

EDIT: on the same computer, loaded with my normal layout, v7.7 uses 0% CPU whilst 7.8 B2 uses 27% CPU.

Philana R. Crouch

Grabbing a process sample will be very helpful.

Already done & email sent to testing:-

"Started Logos with a blank layout and began profiling ASAP. CPU use was 30% - 32% throughout (26% - 28% without the profiler).

No downloads, syncing normally. No user inputs/use."

EDIT: on the same computer, loaded with my normal layout, v7.7 uses 0% CPU whilst 7.8 B2 uses 27% CPU.

Thanks Dave,

I've got a case written up.

Dave Hooton

Just to clarify, after indexing has completed does your CPU stay at a high rate?

I installed the beta update on another machine and Logos also runs with a high CPU usage (28%). When the Indexer was running Logos dropped to 0% CPU, but it resumed at 28% CPU when the Indexer finished!

Philana R. Crouch

The issue with CPU spiking on Windows has been fixed with 7.8 Beta 3 (7.8.0.0013).

Dave Hooton

It has, thank you. Beta 3 is busier than v7.7 when idle, but rarely exceeds 1.0% CPU (max 2.7%).