Nils, This is my recommendation to avoid my worst-case scenario, where someone must go to some far away basement and power cycle the server manually after waiting a couple of days for OOM kicking in. I'm okay with a user using 90% of the ram, if that becomes an issue, I can always email them or kill their process, but more often than not, until I started to use earlyoom is that the memory usage slowly creeps to 100% and the culprit process only gets killed by oom or a power cycle.
Cheers, Edgar On Thu, Jul 6, 2023 at 8:56 PM Michael Orlitzky <mich...@orlitzky.com> wrote: > On 2023-07-06 09:16:46, Nils Bruin wrote: > > > On Wednesday, 5 July 2023 at 08:29:44 UTC-7 Edgar Costa wrote: > > > > > > Hi Gonzalo, > > > > > > I highly recommend using https://github.com/rfjakob/earlyoom instead > of > > > waiting for OOM to kick in. > > > > Wouldn't setting ulimit with -m (memory) or -v (virtual memory) for the > > process that is liable to exceed its memory quota be a more sensible > thing? > > If you don't need a portable solution, then on linux, cgroups are the > most flexible way to leave yourself juuust enough RAM to be able to > move your mouse over the X. > > -- > You received this message because you are subscribed to the Google Groups > "sage-devel" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to sage-devel+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/sage-devel/ZKdiwaZ8lg3aCw3K%40stitch. > -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/sage-devel/CA%2BiQ7x5f%3DzULirZJN5K3F-grgpP6J0ee628cQKGYON_MKbbH_g%40mail.gmail.com.
