dice/impress
1
0
Fork 0
forked from OpenNeo/impress
Code Pull requests Activity

Tighten the RAM limit bounds on the production impress service

Browse source 
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!
This commit is contained in:
Emi Matchu 2023-10-27 10:32:33 -07:00
parent 06258b1dd5
commit af705f1be0
1 changed files with 3 additions and 5 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

8
deploy/files/impress.service
View file

@ -11,11 +11,9 @@ Environment="RAILS_ENV=production"
Environment="EXECJS_RUNTIME=Disabled" Environment="EXECJS_RUNTIME=Disabled"
EnvironmentFile=/srv/impress/shared/production.env EnvironmentFile=/srv/impress/shared/production.env
; Try not to go over 75% of the server's RAM, and kill the app at 80%. ; Try not to go over 1GB of RAM, and kill the app at 1.2GB.
; NOTE: This assumes this is the main thing running on the box! If it were MemoryHigh=1G
; running alongside e.g. a database, you'd want to constrain it differently. MemoryMax=1.2G
MemoryHigh=75%
MemoryMax=80%
; Some security directives, adapted from Akkoma's service file, they seem like sensible defaults! ; 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. ; Use private /tmp and /var/tmp folders inside a new file system namespace, which are discarded after the process stops.