362
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 04 Jul 2023
362 points (96.9% liked)
Privacy
32177 readers
336 users here now
A place to discuss privacy and freedom in the digital world.
Privacy has become a very important issue in modern society, with companies and governments constantly abusing their power, more and more people are waking up to the importance of digital privacy.
In this community everyone is welcome to post links and discuss topics related to privacy.
Some Rules
- Posting a link to a website containing tracking isn't great, if contents of the website are behind a paywall maybe copy them into the post
- Don't promote proprietary software
- Try to keep things on topic
- If you have a question, please try searching for previous discussions, maybe it has already been answered
- Reposts are fine, but should have at least a couple of weeks in between so that the post can reach a new audience
- Be nice :)
Related communities
much thanks to @gary_host_laptop for the logo design :)
founded 5 years ago
MODERATORS
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.
And that's all I needed to know, that is exactly what I thought, you didn't take the time to verify anything.
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.
It doesn't help, because I can't trust it's accurate, and neither should you. As I said, you can't recall what the container was using, you can't tell me any specific numbers like what you might consider to be too high, so how do you expect me to trust that you definitely, for sure would have noticed something that might have been as small as a 300MB swing?
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.
You don't understand my point... I'm not going to trust someone that doesn't know about what it was running at, which is why I asked for specifics on how much RAM it was using. I'm not trusting some random that says, "yeah bro, totally cool, not a problem even though I have no idea about what the RAM was at or even what I would consider to be high, but trust me bro, it's okay. I am soooo vigilante on RAM usage on my server despite having no clue about the RAM usage, but trust me bro, I would know if it was leaking."
No, you can't, not unless you specifically paid attention to it, which you didn't, and that is clear by you not knowing how much it was using. It's possible that every time you checked your overall usage was just after a crash and the container restarting.
That's the reason I asked you to give me specifics on the RAM... because without you being able to provide it, ruled out whether I trusted your opinion.