Beta 5 impossibly slow

I cannot use Beta 5. It is using tons of CPU cycles while I ask it to do nothing. Nothing is downloading, nothing is indexing. The result is that even trying to pop-up a note in a verse in the NASB95 takes forever to appear. Literally 30-60 seconds or more.

Here is the CPU use when I was actually doing nothing at all:

Mark's Test is the one I am using.

I have a number of linked Bibles, study Bibles, and commentaries. Whenever I scroll forward in a Bible Logos 4 goes into hyper CPU use mode for minutes at a time. And I have to wait and wait for the pop-ups to appear again on the text notes.

I do not have any note files open. I have not opened any of the tools that follow what I am doing.

Logos is still running at 78-85% of CPU usage after paging down in my linked Bible two minutes ago. Still no pop-ups over the text notes.

Yesterday I reported how slowly my installation of the beta brought up the parallel resource buttons. Now it is simply unusable.

I will test the timing and CPU use in my non-beta installation after switching user accounts.

Find more posts tagged with

Comments

Todd Phillips

Mark, do you have logging on? The logs would give a good indication of what it is doing.

Mark Smith

https://community.logos.com/discussion/comment/79939#Comment_79939

Yes. Attached.

Tried the same things with the non-beta installation. When scrolling through the NASB95 in the same linked configuration, Logos maxed at about 50% CPU utilization. After paging it took about 5 seconds to return the pop-up functionality in the NASB. I've never felt Logos 4 was a speed demon but the pre-beta version is definitely faster.

5773.Logos4.zip

LaRosa Johnson

I wonder if having two instances open simultaneously is having any impact on its speed

Mark Smith

https://community.logos.com/discussion/comment/79950#Comment_79950

LaRosa,

They were both open when I tested the non-beta version. As you could see from the screen shot the second installation was using NO CPU cycles, so had no impact on the speed of the beta version.

Is is better to use just one from a memory management point of view? I'm sure it is. It is the constant CPU cycles and the inability of the user interface to respond when that is going on that is behind the problem I had.

I did a fair test, even if their might be more optimum ways of running Logos 4.

Jon

https://community.logos.com/discussion/comment/79962#Comment_79962

From your log, looks like it has something to do with parallel resources... There is a bit of a performance crunch as a layout loads and it goes through all your collections getting the parallel resource sets, but yours seems to be doing it over and over again.

Scott H. Clark

https://community.logos.com/discussion/comment/79981#Comment_79981

I experienced the same problem in B4 and also now in B5. Simply scrolling pegs my CPU (99%). And Highlighting a text takes more than 10 secs from the ctrl-k until the highlight appears.

Mark Smith

https://community.logos.com/discussion/comment/79981#Comment_79981

yours seems to be doing it over and over again

That's all I noticed, as well as a bunch of synchronization.

Once my Parallel Resource buttons appeared (some time before I tried to use the program as tested) I would have assumed that that process was complete.

More note files and Parallel Resources are about the only difference between my beta and non-beta installations. That leads me to suspect one or the other.

Mark Smith

https://community.logos.com/discussion/comment/79989#Comment_79989

I experienced the same problem

Not that I want others to have trouble, but I am glad it isn't just me. Thanks.

Russ Quinn

https://community.logos.com/discussion/comment/79994#Comment_79994

I am feeling for you guys but I must report that Beta 4 and 5 are noticeably faster in every aspect for me.

Mark Smith

https://community.logos.com/discussion/comment/80013#Comment_80013

Beta 4 and 5 are noticeably faster in every aspect for me

Russ, do you have time to count and report how many collections you have? Also have you removed any of your collections from appearing as parallel resources? Just wondering if this could have something to do with it.

Russ Quinn

https://community.logos.com/discussion/comment/80053#Comment_80053

Beta 4 and 5 are noticeably faster in every aspect for me

Russ, do you have time to count and report how many collections you have? Also have you removed any of your collections from appearing as parallel resources? Just wondering if this could have something to do with it.

Mark,

One of the first things I did when they added the All parallel resources as a default group was to uncheck the Include option in each of my collections.

I am currently relying on the All parallel resources and my prioritization. It seems to give me everything I need for now. I am primarily using the Parallel resources to quickly run through commentaries on various passages.

But when I say every aspect being faster, I'm also talking about returning results for morph searches, updating the results of the analysis view as I scroll down a long list, opening the library, and just general responsiveness.

Dave Hooton

https://community.logos.com/discussion/comment/79991#Comment_79991

yours seems to be doing it over and over again

That's all I noticed, as well as a bunch of synchronization.

Once my Parallel Resource buttons appeared (some time before I tried to use the program as tested) I would have assumed that that process was complete.

More note files and Parallel Resources are about the only difference between my beta and non-beta installations. That leads me to suspect one or the other

The repetition of collection searches is inherent to Parallel Resources and Bradley commented on making improvements at http://community.logos.com/forums/t/10113.aspx. However, the impact for me has been that it takes 2-3 seconds for the PRA icon to appear after each switch to a resource. It's distracting when you have to wait for it.

I don't have any note files!

Mark Smith

https://community.logos.com/discussion/comment/80068#Comment_80068

The repetition of collection searches

I guess that's what is killing me both when starting up and when using Logos 4 Beta 5. I can live with the start-up lag because I usually leave Logos open, but the drag on the CPU and impossibly slow response times after start-up are impossible to work with. If constant collections searches are the culprit then they need to be eliminated.

Thanks for the info.

Mark Smith

https://community.logos.com/discussion/comment/80063#Comment_80063

One of the first things I did when they added the All parallel resources as a default group was to uncheck the Include option in each of my collections.

Well I have 120 collections and unchecked about 2/3 of them when I was getting 5 and half minute lags at start-up (cut the lag to 3 and a half).

Of course for me everything is slower because the CPU is bustin' almost constantly. Checking and rechecking my collections I guess.

Bohuslav Wojnar

https://community.logos.com/discussion/comment/80073#Comment_80073

Mark, I think it is the number of collections you have. I have just about 25 of them and I do not see that dramatic slow down. I have most of them included in my parallel resources. But also notes, I do not have hundreds of them. So it might be this also. I don't know.

EDITED: It's true when I open a resource, before it finds the parallel resources (and icon appears) the CPU goes to 100%. It takes about 3-5 sec. to my notebook.

Todd Phillips

https://community.logos.com/discussion/comment/80122#Comment_80122

Mark, I think it is the number of collections you have. I have just about 25 of them and I do not see that dramatic slow down. I have most of them included in my parallel resources. But also notes, I do not have hundreds of them. So it might be this also. I don't know.

I noticed that the collections definitions are constantly being logged to the log file when the library window is open. Perhaps this is affecting the performance as well. Stuff like this:

2010-01-19 21:31:47.4365    64    Info    LibraryCatalogIndex    Searching for all records matching: title:"Christ"
2010-01-19 21:31:47.5215    68    Info    LibraryCatalogIndex    Searching for all records matching: type:dictionary -greek -hebrew -syriac -aramaic -encyclopedia -dictionary
2010-01-19 21:31:47.5425    59    Info    LibraryCatalogIndex    Searching for all records matching: type:bible -greek -english -syriac -coptic -arabic -aramaic
2010-01-19 21:31:47.7835    68    Info    LibraryCatalogIndex    Searching for all records matching: type:"Media Collection" -story
2010-01-19 21:31:47.8395    59    Info    LibraryCatalogIndex    Searching for all records matching: type:"Bible Harmony" -gospel
2010-01-19 21:31:48.1625    68    Info    LibraryCatalogIndex    Searching for all records matching: atlas
2010-01-19 21:31:48.2185    64    Info    LibraryCatalogIndex    Searching for all records matching: type:topical
2010-01-19 21:31:48.3205    56    Info    LibraryCatalogIndex    Searching for all records matching: type:dictionary english +Merriam
2010-01-19 21:31:48.4315    68    Info    LibraryCatalogIndex    Searching for all records matching: type:bible -greek -english -syriac -coptic -arabic -aramaic
2010-01-19 21:31:48.4925    64    Info    LibraryCatalogIndex    Searching for all records matching: archeology
2010-01-19 21:31:48.5195    68    Info    LibraryCatalogIndex    Searching for all records matching: type:"Bible Harmony" -gospel

Robert Pavich

https://community.logos.com/discussion/comment/80178#Comment_80178

Just in case this has something to do with it..if you'll notice, L4 now keeps it's place in the interlinear panel while you scroll....that's a real performance sucker...

I close the interlinear while I scroll...

Mark Smith

https://community.logos.com/discussion/comment/80181#Comment_80181

I close the interlinear while I scroll...

Mine are not open, so that isn't it. It seems that it has something to do with rechecking my collections over and over as Todd pointed out.

Todd Phillips

https://community.logos.com/discussion/comment/80316#Comment_80316

I close the interlinear while I scroll...

Mine are not open, so that isn't it. It seems that it has something to do with rechecking my collections over and over as Todd pointed out.

Bradley said that the logging comes from the program checking the collections for parallel resources for each resource window:

http://community.logos.com/forums/p/10142/80291.aspx#80291

Mark Smith

https://community.logos.com/discussion/comment/80326#Comment_80326

From my perspective I'd like to know if there is going to be a solution. The current state of affairs renders the beta totally unusable. It would seem that constantly checking collections is unnecessary. Perhaps there needs to be a re-think about how the parallel resources are determined. I am using immense numbers of CPU cycles just to get them to show up in the first place and then the constant grinding after that slows everything almost to a stand-still. I know collections are dynamic, but can't there be a way to flag when a change in a collection has been made? It might take some work, but then only collections that have changed would need to be updated. There could be a static database established once with all parallel resource associations, and then only as needed would it be updated.

Maybe this isn't the issue, but if it is, I for one need Logos to address it.

By golly this program is a resource hog! It is only getting worse as new 'features' are added. What is it going to be like when everything is added back in?

Bradley Grainger (Logos)

https://community.logos.com/discussion/comment/80362#Comment_80362

One of our goals in beta testing is to collect performance feedback information and determine where we need to make improvements. This feature has not been optimised, but doing so is on our tasklist.

BillS

https://community.logos.com/discussion/comment/80362#Comment_80362

Hi Mark,

(WARNING: HUMOR FOLLOWS)

Are you sure it isn't the number of times per minute you're checking for another beta?

[;)]

Mark Smith

https://community.logos.com/discussion/comment/80382#Comment_80382

HMMM. That affects my speed? Honestly I was more worried about the number of trips to the kitchen I was making while waiting for Logos to return control to me the user.

Mark Smith

https://community.logos.com/discussion/comment/80368#Comment_80368

This feature has not been optimised

I'm glad you didn't say 'this feature has been optimized.' Thanks for the response, Bradley, but I am out of the water for beta testing until something gets better. Ah, well.

Dewayne Davis

I had similar results after installing B4 this morning. I got some kind of Windows 7 shut down error while the installation restarted and the library was initializing. However with B5 it is actually running faster than it ever has. I wonder if possibly something failed during the installation? It would be nice to see a 'repair' option in Logos 4 similar to the option in Office.

J. Morris

https://community.logos.com/discussion/comment/79989#Comment_79989

I experienced the same problem in B4 and also now in B5. Simply scrolling pegs my CPU (99%). And Highlighting a text takes more than 10 secs from the ctrl-k until the highlight appears.

Having similar issues

Fred Chapman

https://community.logos.com/discussion/comment/80368#Comment_80368

One of our goals in beta testing is to collect performance feedback information and determine where we need to make improvements. This feature has not been optimised, but doing so is on our tasklist.

I am having a speed issue with Beta 5 as well that did not show up in the other Betas. Being somewhat new to L4 I only have 28 collections. I have recently upgraded to Platinum and I am not sure if that is affecting the speed. I tried clearing all the links in my study layout and something as simple as scrolling still jumps CPU usage to near or at 100%.

On a more positive note, I thank God for Logos and L4. I was a long time user of L3 and it was great; but L4 and the potential it has takes my study and understanding of God's word to another level. Thank you for your vision and hard work. God is using you in a unique and powerful way.

Icarus38376

https://community.logos.com/discussion/comment/80326#Comment_80326

Similar situation. I have a passage guide open, a KJV and a commentary. Nothing else. If I scroll the KJV and highlight a verse the CPU pegs out (also my music begins stuttering). If I copy the text, it takes over 10 seconds to complete he copy, until the CPU calms down.

Not complaining, just commenting.

Addendum: If I close everything but the KJV the same symptoms occur.

Bottom Line...Text Scrolling pegs the CPU...

Dave Hooton

https://community.logos.com/discussion/comment/80806#Comment_80806

I've observed a lot of inefficiency in the logs connected with Parallel Resource and searching a collection, which Bradley is aware of. It might help to produce a log when you experience a slowdown, noting the time.

Icarus38376

https://community.logos.com/discussion/comment/80961#Comment_80961

Here is a log that shows at 20:19 where I start to scroll. It looks like it is parsing through all my collections each time I scroll.

BTW most of my collections are based on "mytag"

7752.Logos4.log

SteveF

https://community.logos.com/discussion/comment/80368#Comment_80368

One of our goals in beta testing is to collect performance feedback information and determine where we need to make improvements.

Bradley, this was not 'logged"

Yesterday Logos 4 ran all day as I continually went back and forth from it to other tasks. I had in a separate window the tools that often slow Logos 4 (at least for me- the"follow" tools like "Power" & Explorer etc.)

I was systematically going through a list of 40 resources, using the Right arrow key to load and then switch, one at a time. By evening and at about the 20th I too was getting "slow" results. I happened to look at the Task Manager and Logos4 's Mem use was up over 600,000. I had not seen that since much earlier in beta (sometime during the fall months)

Question:.It is possible that some of the recent additions (perhaps related to Resource associations, etc) have memory 'leaks' that have not yet been noticed?

Thanks

Dave Hooton

https://community.logos.com/discussion/comment/80987#Comment_80987

Here is a log that shows at 20:19 where I start to scroll. It looks like it is parsing through all my collections each time I scroll.

I replicated your log activity from 22:19 by opening KJV1900 and just scrolling with the mouse. No wonder it was so jerky, repeatedly searching collections and (in my case) storing temporary search results! But that activity continued when I wasn't doing anything!

BTW have you now changed that "all resources" collection to use rating:>=0?

Icarus38376

https://community.logos.com/discussion/comment/81478#Comment_81478

Yes, I changed the "all resources" collection, and I turned off the "show in parallel resources" option for all the other collections. Also, I have some visual filters that when turned off speed things up as well. Performance is not great, but it's at least usable. I think ultimately that the "all resource" hack I had was the same impact as about 30 individual collections.

Thanks for your help.