β2 is extremely processor hungry

Just for what it's worth before things are optimized.  I've noted that Beta2 is extremely needy of my processor on a regular basis. 

The graphic below is a 60 second snapshot showing overall processor usage.  The orange line is Logos 4.

 

I have noticed this CPU signature in the past.  But I'm not seeing it now, however my Logos usage has been light since I started it today.  Yesterday, Logos4's memory usage was around 500MB,  today it's sitting around 250MB.  Perhaps the CPU usage is related to a component that's only loaded on demand.

You're not indexing anymore, right?

On my Intel Core 2 Duo P7370 2.0GHz Logos is jumping to the top of the Task Manager list every few seconds with about 8% usage (sometimes as high as 20%). It and MS Word seem to be taking turns topping the scale; perhaps they are dancing. Logos4 is using 230MB of memory. Logos is obviously continuously doing something in the background even when it's just sitting there.

Tom

Todd,

what are your system specs?  20% is much lower than 50% of mine.  I wonder if the processor makes a difference?

My system is a 5 year old single core Pentium M 2GHz.  Not exactly top of the line anymore.

I'd already reported this, but it had no reply - I was wondering if it was just my machine. I have a very similar pattern of regular 50% CPU spikes on a dual core machine - it seems to happen in bursts.

Today when the program crashed while trying to print the Mem Usage was up to 600,000K and I watched it climb to about 800 or 900000K before I rebooted. Right now after a reboot it is only at 207,000K.

Steve

Ah, I see that Logos4Indexer.exe has its own line in the Task Manager and is also using an additional 254,600 K of "Mem Use"

I have turned everything else off except for my Thunderbird (Firefox) email.

I've been following this thread and noticed my CPU usage has at times pegged all the way up to 100%, also. The odd thing about it is, it's not a consistent problem!  It was definitely higher when indexing occurred during the first beta install from the DVD and also the indexing when updating to beta2.

This is an observation - I do not have any expertise in this area:

This afternoon I had the program (Beta 2) open for about 2.5 hours.

I did a Passage Guide; a "search all my computer"; edited a handout etc; "explored" Bible Explorer and clicked on a number of its "cited" links etc.

Finally  I decided to do a simple restart of the program because I had run out of memory - it had gotten up to 900,000K

Once re-started it settled in at the 190,000K level.

I have a tray indicator that lets me know when available memory is low. It probably saved me from freezing up entirely (as happened last week).

I don't know if this is something that can be optimized (like indexing) or is just something that I will have to put up with on my older P4 single core.

But I have seen questions/comments relating to 'memory leaks" or of the program not "releasing" memory back.

thanks

Steve

I can get it up to 500K+ but I can't make it hit 600K of RAM. It also seems to be releasing RAM and dropping back to 300K+ quite readily. I am using Vista Business SP2 with no RAM management utility. I will leave it for 2 or 3 hours and see what it's at when I return.

Tom

Update - It's holding steady under 500K K

I haven't observed processor usage but B2 operations do slow dramatically after c. 2-3 hours of use. Just trying to change a text search can be exasperating and tab opens and closes get up to 10 second mark.

My experience makes me think that the more windows open the slower it is, i.e.  things speed up again when you close resources. I've had my current instance running for a couple days now, and it's still basically the same speed as when I started.  But that's hard to quantify, especially since I've just used it sparingly (reading, no reports) during that time.

Tom,

you know what's weird?

I have a 3 year old dell Core Duo 1.8ghz laptop. I can work, use Logos, and do anything while this thing is indexing; it doesn't slow it down a bit.