Normal
0
February 24, 2010
My computer has the following processor and memory:
Processor x86
Family 15 Model 6 Stepping 5 GenuineIntel ~3000 Mhz
Total Physical Memory 2,048.00
MB
Available Physical Memory 1.53
GB
Total Virtual Memory 2.00
GB
Available Virtual Memory 1.96
GB
Page File Space 3.82 GB
These memory specs were taken with Logos 4 open.
The following is my Logos 4 Layout:
The Logos 4 window contains two tiles containing four panels
and six panels. All the panels contain commentaries. So there are a total of
ten commentaries.
In addition I have four floating windows. One contains the
Highlighters, and another contains Help. A third contains six Bibles, and the
last one contains five dictionaries.
My problem is performance.
Now, I can hear you laughing at me. "You have too many
resources open", you're saying. And I agree ... at least partially.
If I close enough resources I get acceptable performance. At
least we agree on this point.
But why shouldn't I be able to open a lot of resources? I've
got plenty of memory, a respectable processor, and I'm not doing anything
except reading my commentaries. Oh all right, once in a while I click on a
reference, and my floating window of Bibles pops up to show me the verse. And
once in a while I'll look up something in a dictionary. That's about it.
That was the executive summary. Let me give you some
definitions followed by some hard data.
Opening resources: I define the time to open a
resource as the elapsed time from clicking the resource's tab until the
resource is displayed, and the keyboard and mouse are no longer frozen.
Stepping through a resource: I define the time to
step through a resource as the elapsed time from pressing any of the following
keys "Page Up", "Page Down", "Arrow Up", or
"Arrow Down" until the resource is re-displayed, and the keyboard and
mouse are no longer frozen.
The Data:
It takes 12 to 14 seconds to open any of my commentaries or
Bibles.
For some unknown reason it takes 27 seconds to open the
MacArthur Study Bible NASB.
Similarly, it takes 12 to 14 seconds to perform a "Page
Up", "Page Down", "Arrow Up", or "Arrow
Down" operation in a Bible or commentary.
Now, here's one last anecdote. When I try to select text
with the mouse, say for instance one short Bible verse, I will very often get
all but the last two or three characters selected when Logos 4 starts using
50-60 percent of the CPU (as reported by the Task Manager). At this point the
selection process is frozen. But if I'm patient, and keep my hand steady, and
the left mouse button depressed for 12 to 14 seconds I can continue selecting
the remainder of the verse. Once the selection process is complete, I have to
wait 12 to 14 seconds again before I can copy the verse.
That's it. I'm open to any and all suggestions for improving
my system's Logos 4 performance.
I know, I know, I need a new computer. Unfortunately, that's
not an option right now.
Also, if anyone has a clue as to what Logos 4 is doing while
I'm waiting in the above examples, I'd love to hear what you think.
By the way. Every other program on my computer (and I've got
a lot) performs just fine.
Doug Witmer
