Auto-populating: why so slow???!!!
I have always found auto-populating a read drag. In fact, it infuriates me how much time it takes.
I've had quite a good processor for a while but was making do with 4 gb. of ram. I increased it to 8 gb. Logos 7 runs faster (it ran well with 4 gb. too), but auto-populating is still a drag.
Now I know it's the first time auto-populate is called on in a session that is slow, but I just don't understand why. Why, since my resources are the same, must auto-populate be doing some sort of indexing every time I run a new session? It is inefficient and time-wasting and I am tired of it.
When I am in a rush, I often give up on what I was planning to look up: is that what I paid all this money for???
When I consider how much time general indexing already takes whenever I download something new.. and BTW, even though the process is set to low priority, it is still quite a resource hog. Logos regularly freezes momentarily during indexing (typically for just 1 new resource) and the whole system slows down. When I am working, I have to turn off indexing for 4 hours to regain control of my system. Again, "working around" the slow downs of Logos.
I am just fed up with having to put up with this. I don't want another blab that tells me that it's normal. It should not be. Please fix it.
Comments
-
what do you mean by "auto populate"?
macOS, iOS & iPadOS |Logs| Install
Choose Truth Over Tribe | Become a Joyful Outsider!0 -
Whenever one has to use a field (Factbook, Passage Guide, etc.) to indicate one's query and auto-populates runs to propose matches.
Example: if one types "Isaiah," the book of, person of, events attached to, etc., will be produced in a drop-down list for which one has to wait patiently if it so happens to be the first time auto-populate has been needed in that particular Logos session.
0 -
I don't use facebook often. I just opened it and checked my system, and it took about 10 seconds the first thing I checked. All others were under 1 second. Is that what you are seeing?
macOS, iOS & iPadOS |Logs| Install
Choose Truth Over Tribe | Become a Joyful Outsider!0 -
Thanks for the report on this. We do currently have a case open for this problem, and we have recreated the issue. We've added a link to this thread to the case so that we can post an update when we find a solution.
Andrew Batishko | Logos software developer
0 -
Thank you, Andrew, for the reply and info. I hope it will all get sorted out sooner than later.
0 -
Any drop down list in the software takes forever to auto-populate, even after the first use it can be infuriatingly slow.
Francis said:I have always found auto-populating a read drag. In fact, it infuriates me how much time it takes.
I've had quite a good processor for a while but was making do with 4 gb. of ram. I increased it to 8 gb. Logos 7 runs faster (it ran well with 4 gb. too), but auto-populating is still a drag.
Now I know it's the first time auto-populate is called on in a session that is slow, but I just don't understand why. Why, since my resources are the same, must auto-populate be doing some sort of indexing every time I run a new session? It is inefficient and time-wasting and I am tired of it.
When I am in a rush, I often give up on what I was planning to look up: is that what I paid all this money for???
When I consider how much time general indexing already takes whenever I download something new.. and BTW, even though the process is set to low priority, it is still quite a resource hog. Logos regularly freezes momentarily during indexing (typically for just 1 new resource) and the whole system slows down. When I am working, I have to turn off indexing for 4 hours to regain control of my system. Again, "working around" the slow downs of Logos.
I am just fed up with having to put up with this. I don't want another blab that tells me that it's normal. It should not be. Please fix it.
0 -
Three months later... no news? Still an irritating problem and real time-waster.
0 -
I have had the same experience. Makes looking up scripture references in the passage guide insanely slow. Usually takes several minutes for the options to show! I no longer use the passage guide as often because of this! I typically just go open a commentary from the library instead! I haven't posted anything about it simply because I had no idea what to call it. Thanks Francis!
0 -
Bump (exponentially)!!!
PLEASE do something about this!
I commonly find myself turning away from the command box to more immediate alternatives. For instance, I wanted to quickly access a work by an author with a unique name. I typed the author's name in the command box to see corresponding resources (I have only one) listed. It started doing its slow processing routine. Since I have better things to do than wait around. I just clicked on the library icon instead to find my resource.
This is a scenario that repeats almost daily.
By far the most common for me is to choose to go command box "Open Passage Guide to Mark 6:4" rather than open the Passage Guide tool directly and type in Mark 6:4 and then wait around. I know that in this case the command box workaround is faster, but the problem is the same as above: slow, slow, slow presentation of choices.
But responding to this issue is apparently even more frustratingly SLOW!
[:@]
0 -
The same issue with the Topic Guide, maybe worse. Please address this slowdown as requested above.
0 -
John Fidel said:
The same issue with the Topic Guide, maybe worse. Please address this slowdown as requested above.
Yes, it pretty much applies wherever a field attempts to match a string with a list of matching propositions.
0 -
Francis said:
Yes, it pretty much applies wherever a field attempts to match a string with a list of matching propositions.
Me too. Except I haven't had the issue as long as has been reported in this thread. Mine started a month or so ago. I thought I was typing wrong, as hitting enter after typing a passage did nothing. Then, eventually I realized that as I was typing, nothing populated.
Its pretty much always slow now, but it varies in how slow it is. Sometimes I can get a hit in 5 seconds, but sometimes its 15-30 seconds - and I'm on a mack daddy iMac. lol.
Myke Harbuck
Lead Pastor, www.ByronCity.Church
Adjunct Professor, Georgia Military College0 -
The general slowness of Logos is infuriating, and is a great disincentive for me to use Logos more frequently. In general, even though it's loaded (bloated?) with heavy-duty features and even though I (and many other users) have invested heavily in the software and resources, its grinding slowness makes it feel old and tiring. Logos is not a delight to use. Add to that its user-unfriendliness (e.g. the unmanageable search syntax that FL refuses to simplify). Many many times I find myself popping over to Google to quickly find the answer I need within seconds.
FL is well aware of these problems. But in a way FL is acting very much like Microsoft: Give us expensive, bloated, slow software and when we complain about the slowness, they advice us to invest more money by throwing hardware at the problem. If we complain again, they open a ticket and go away for months (years sometimes) or send you to "uservoice".
0 -
Francis said:
Bump (exponentially)!!!
PLEASE do something about this!
Concur so added reply to Logos 8 Wishlist about automatic search assistance annoyance (along with dreaming about program setting to enable/disable search assistant as desired).
Keep Smiling [:)]
0 -
Just stumbled across another problem that was really caused by the bug. 10 months later, I wonder what the delay is in fixing this? I have a fast Mac, and just typing Bible references in takes around 17 seconds!!!!
0 -
Don Awalt said:
Just stumbled across another problem that was really caused by the bug. 10 months later,
As I posted on that other thread, this is a different problem (a new performance regression introduced in Logos 7.11).
0 -
The same occurs in the Sermon Editor when you want Logos to fill in the Topic and Scripture fields.
0
