Ruud@lemmy.worldM to Lemmy.World Announcements@lemmy.world · edit-21 year agoSome system load graphs of last 24hlemmy.worldimagemessage-square199fedilinkarrow-up11.43Karrow-down113file-text
arrow-up11.41Karrow-down1imageSome system load graphs of last 24hlemmy.worldRuud@lemmy.worldM to Lemmy.World Announcements@lemmy.world · edit-21 year agomessage-square199fedilinkfile-text
minus-squareaussiematt@kbin.sociallinkfedilinkarrow-up2·1 year agoFrom those graphs, memory usage is very low. Most of it is being used for disk caching, which is what linux does with memory it has no other use for (may as well use it for something).
minus-squareRuud@lemmy.worldOPMlinkfedilinkarrow-up1·1 year agoYes, but we still restart the containers every 30 min. I’m gonna see if that’s still needed after the recent changes.
minus-squarePerhyte@lemmy.worldlinkfedilinkEnglisharrow-up1·1 year agoAh, so that’s the reason for the regular dips in the memory graph I assume? They do indeed seem to be spaced every 30 minutes.
minus-squareFermatsLastAccount@lemmy.worldlinkfedilinkarrow-up1·1 year agoThe consistent, sharp dips every 15 minutes made me assume that the container was being restarted.
From those graphs, memory usage is very low. Most of it is being used for disk caching, which is what linux does with memory it has no other use for (may as well use it for something).
Yes, but we still restart the containers every 30 min. I’m gonna see if that’s still needed after the recent changes.
Ah, so that’s the reason for the regular dips in the memory graph I assume? They do indeed seem to be spaced every 30 minutes.
The consistent, sharp dips every 15 minutes made me assume that the container was being restarted.