You're viewing part of a thread.
None - I deleted it because I don't use it anymore. It wasn't much though and it never bloated, even when running for over a whole month.
Permanently Deleted
No, I didn't check because it never got so big to the point where it would become suspicious to me that something might be wrong. Maybe it uses more RAM than other self-hosted search engines but it never leaked memory so it used more and more RAM the longer the instance ran. Just because it uses much RAM it doesn't mean it's leaking memory. It might just be developed badly, not very caring about your ressources.
Permanently Deleted
Yes, because as I said it's not a memory leak. I would have noticed a memory leak because I keep an eye on the ressources of my NAS (on which my SearXNG instance was hosted) and I didn't notice an usual growing consumption of my RAM. I just didn't check the consumption of RAM on each individual container that was running. I would have done that if I would have noticed an unusual consumption of RAM.
Look, I can't give you more detailled information than this because it's all from my memories. All I wanted to do was to help as good as I can by answering from my experiences. If that doesn't help or is inappropriate to you I'm sorry. I didn't want to offend you or anything like that.
Permanently Deleted
Do you understand how this is not helpful in any way now?
No, because you're just talking about how much RAM SearXNG consumes. In your original post you were complaining about a memory leak. I monitor the ressources of my NAS. Even after a restart of my NAS where every container was freshly started the RAM consumption wasn't higher than a month later after the restart (without restarting any of the docker containers). And that is why I can with full conviction tell that my SearXNG instance didn't leak memory.
This discussion is going nowhere from here so I'm gonna stop responding. I said everything to make my point as clear as possible. Have a nice day.
Permanently Deleted