Skip to main content

max / makenotwork

1.0 KB · 23 lines History Blame Raw
1 # Room for the test suites PoM now schedules.
2 #
3 # The base unit caps the whole cgroup at 256M, which is generous for the daemon
4 # and nowhere near a cargo build. The suites run as child processes in this same
5 # cgroup, so the cap applies to them: left at 256M every scheduled run would be
6 # OOM-killed and land in the dashboard as a failing suite. astra has 125G.
7 #
8 # 48G rather than 16G because the MNW server workspace blew through 16G and 20G
9 # of swap before dying. run-ci.sh also caps cargo's job count: 96 cores means 96
10 # concurrent rustc processes by default, and the memory ceiling is the wrong
11 # place to discover that.
12 #
13 # ProtectHome drops to read-only rather than staying true because the staging
14 # clones fetch from the mirrors under /home/max/git-mirrors. Read-only is the
15 # whole requirement: nothing here writes outside /var/lib/pom.
16 [Service]
17 MemoryMax=48G
18 ProtectHome=read-only
19 Environment=HOME=/var/lib/pom
20 Environment=CARGO_HOME=/var/lib/pom/.cargo
21 Environment=RUSTUP_HOME=/var/lib/pom/.rustup
22 LimitNOFILE=65536
23