Slow Downs

ASUNDER

I've been having lots of slow downs recently. Didn't complain about them until now when it got really bad. I've had maybe two Bibles open and a couple passage lists and I have like a five second latency when focusing tabs and other tasks. Then the program freezes, 'isn't responding' it crashes one of my Bibles then reloads it again. This takes like ten seconds, just to focus that tab.

I can complain about a lot of other minor things, but something like this is a deal breaker.
A Windows 10 application running nothing but text can't be having these issues in 2025. This is not acceptable. Logos isn't a 3D video game running max settings and it isn't the year 1998. I have a four thousand dollar computer. I've seen it do incredible things in the blink of an eye. It should be able to manage basic text files without issue.

What is slowing down Logos? I checked and my cpu and ram were fine when it was happening. I don't know how to force high priority processing.

MJ. Smith

Are you using several visual filters? or on the fly collections?

ASUNDER

I don't know what those things are. That reminds me, it does slow down with maps or picture books too.
If I have a Bible open I always have a couple of reformats going, if that's a visual filter.

I'm thinking of some possible causes.

The Documents tool might be a cause. I have a lot of book collections and passage lists now.
The method of opening a tool and it automatically listing everything is a bad method in my opinion. We very rarely go to use a tool because we want to look at everything in that tool. I think tools like documents should start off blank. You would have to manually click on 'All' to populate the All list. This would speed up tool load times too.

In my complaint about loading an entire Bible in one window, I think this contributes to slow down too.
With a single Bible open Logos is using 500MB of RAM. That's a lot for a simple text file. If I compare it with Notepad++ running a text file it's 16MB. That low range of use is more appropriate for text. I have 64GB of RAM but used RAM still needs to use constant power, so I don't like the energy waste, if nothing else. If an app is going to use resources there should be a reason for it.

I can run FL Studio, almost maxing out my computer and there still isn't any input lag. Until it is maxed out. Real time audio processing is one of the hardest tests of a computer and mine can reasonably do it no problem, so a text files app shouldn't be a problem.

But my top suspicion right now is the internet. Anything I do, I see Logos doing the sync animation. So it might be intercepted by my antivirus, checking if this data transfer is malicious. So Logos has to wait for it to be approved. That might explain the bottleneck I think. So I don't think Logos needs to be syncing all the time. We should be able to change Logos to manual sync; we click the sync button and it would sync all the changes made since the last sync, and when closing Logos.

Otherwise I don't really know what's wrong. Most times Logos is snappy, sometimes it's not.

EastTN

The method of opening a tool and it automatically listing everything is a bad method in my opinion. We very rarely go to use a tool because we want to look at everything in that tool.

Agreed.

So I don't think Logos needs to be syncing all the time. We should be able to change Logos to manual sync; we click the sync button and it would sync all the changes made since the last sync, and when closing Logos.

Agreed.

Sometimes less is more.