From af705f1be05ab01bebb36f4e3944ec6a3f6372f0 Mon Sep 17 00:00:00 2001 From: Matchu Date: Fri, 27 Oct 2023 10:32:33 -0700 Subject: [PATCH] Tighten the RAM limit bounds on the production impress service Lol ok, as I had kinda predicted, the memory bounds I set last time were not tight enough, and it stalled out again! (It was at 75% and fully just not working.) Let's try this tighter bound instead! --- deploy/files/impress.service | 8 +++----- 1 file changed, 3 insertions(+), 5 deletions(-) diff --git a/deploy/files/impress.service b/deploy/files/impress.service index 7f0ad300..7f4a0702 100644 --- a/deploy/files/impress.service +++ b/deploy/files/impress.service @@ -11,11 +11,9 @@ Environment="RAILS_ENV=production" Environment="EXECJS_RUNTIME=Disabled" EnvironmentFile=/srv/impress/shared/production.env -; Try not to go over 75% of the server's RAM, and kill the app at 80%. -; NOTE: This assumes this is the main thing running on the box! If it were -; running alongside e.g. a database, you'd want to constrain it differently. -MemoryHigh=75% -MemoryMax=80% +; Try not to go over 1GB of RAM, and kill the app at 1.2GB. +MemoryHigh=1G +MemoryMax=1.2G ; Some security directives, adapted from Akkoma's service file, they seem like sensible defaults! ; Use private /tmp and /var/tmp folders inside a new file system namespace, which are discarded after the process stops.