this post was submitted on 21 Jan 2024
82 points (100.0% liked)

Science Memes

234 readers
52 users here now

Welcome to c/science_memes @ Mander.xyz!

A place for majestic STEMLORD peacocking, as well as memes about the realities of working in a lab.



Rules

  1. Don't throw mud. Behave like an intellectual and remember the human.
  2. Keep it rooted (on topic).
  3. No spam.
  4. Infographics welcome, get schooled.

This is a science community. We use the Dawkins definition of meme.



Research Committee

Other Mander Communities

Science and Research

Biology and Life Sciences

Physical Sciences

Humanities and Social Sciences

Practical and Applied Sciences

Memes

Miscellaneous

founded 2 years ago
MODERATORS
 
you are viewing a single comment's thread
view the rest of the comments
[–] MBM@lemmings.world 2 points 9 months ago (2 children)

Are images from mander.xyz broken for anyone else?

[–] fossilesque@mander.xyz 3 points 9 months ago* (last edited 9 months ago) (1 children)
[–] Sal@mander.xyz 5 points 9 months ago* (last edited 9 months ago) (1 children)

Thanks. I noticed and reset the server a few minutes ago.

Something has been off recently. The CPU is spiking and the RAM gets used up, which crashes the pict-rs container. The pict-rs won't reconnect until I reset the lemmy Docker container.

I doubled the RAM and added one core, but that was not enough to stop this problem, which means that whatever is causing these spikes is unconstrained. I need to look more deeply into Docker memory management to see if I can limit RAM usage such that the crash can be avoided while remaining functional.

[–] fossilesque@mander.xyz 2 points 9 months ago (1 children)
[–] Sal@mander.xyz 5 points 9 months ago

Thanks. I have looked into it a bit more and I think that it is the postgres database grabbing all the memory it can. I have set a hard limit for the postgres container. Hopefully this resolves the problem!

[–] Sal@mander.xyz 3 points 9 months ago* (last edited 9 months ago)

Yes, sorry. It is a problem that started over the weekend. I thought I had patched it by doubling the server's RAM and adding a core, but that was not enough. Some process is causing the RAM use to spike and the image backend is crashing because of that.