this post was submitted on 04 Jul 2023
309 points (96.7% liked)

Privacy

31946 readers
673 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

Related communities

Chat rooms

much thanks to @gary_host_laptop for the logo design :)

founded 5 years ago
MODERATORS
 
you are viewing a single comment's thread
view the rest of the comments
[–] somedaysoon@lemmy.world 0 points 1 year ago* (last edited 1 year ago) (1 children)

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?

[–] Vexz@feddit.de 1 points 1 year ago (1 children)

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.

[–] somedaysoon@lemmy.world 1 points 1 year ago

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."

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.

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.