Memory usage

[Arcanemuse]

On my desktop, SwordSearcher is using 542MB of ram. I noticed this when I was having issues with high memory usage. I shut down some memory hogs and all is better but that shouldn't be like that. On my laptop, it's using about 4MB. I'm puzzled. I don't understand why it's using all that memory on the desktop. Any ideas? It's on Win 11. I'd blame an update but the laptop gets the same ones. No known viruses either. I've done recent scans. Also have run Malwarebytes for any other surprises. Nothing found. This is crazy as it is using more memory than any other program on my system at this point, including Logos. LOL Sorry for the double post. I thought the first one got lost.

 

[kjv777]

I am using 28mb of memory on Windows 11 Pro. SwordSearcher 10.0 (10.0.5.26020 x64)

 

[Brandon Staggs]

500MB really isn't much on a modern system. I've got apps sitting idle right now eating 1.5GB. SwordSearcher loads and keeps a fair amount of data "warm" in memory as you use it (Bible text, indexes, modules you've opened, search caches, etc.) so it can respond instantly instead of hitting the disk every time.

The desktop vs. laptop difference almost certainly isn't that your desktop is doing something wrong, it's that the two machines are in different states. If the laptop is showing 4MB, that usually means SwordSearcher just launched, or Windows has paged most of its working set out because something else needed the RAM. Use it for a while on the laptop and you'll see that number climb too. Or look at it on the desktop right after a fresh launch and you'll see it start small.

The important thing: if another program actually needs the memory, Windows will reclaim it from SwordSearcher automatically. Unused RAM is wasted RAM. The OS would rather let an app keep useful data cached than have it sit empty. So when you saw memory pressure and shut down some other programs, that freed things up; SwordSearcher would have given memory back on its own if it had to.

Nothing to worry about here. It's working as intended.