~ knotless Search/
↑↓ move↵ open⇧↵ all results

chadtmiller.com/knotless

git that lives in your Atmosphere account

knotless.dev
1 collaborator

knotless 0.13.0 Latest 2 packages, 1 image

1
10

Each run on the runner host has 12 GiB, so test builds three crates at once

Merged chadtmiller.com asked to merge into main from chadtmiller.com/knotless:perf/build-memory
.knotless/workflows/deploy.yml+1−1
@@ -80,7 +80,7 @@ env:
KNOTLESS_RUNNER_ARGS: --queue --unmetered did:plc:bcgltzqazw5tb6k2g3ttenbj --unmetered did:plc:e7rftrdyz5e2rw4y6ocszew2 --trust did:plc:bcgltzqazw5tb6k2g3ttenbj --trust did:plc:e7rftrdyz5e2rw4y6ocszew2 --pull-jobs 4
KNOTLESS_RUNNER_CPUS: "4"
KNOTLESS_RUNNER_JOBS: "4"
KNOTLESS_RUNNER_MEMORY: "10"
KNOTLESS_RUNNER_MEMORY: "12"
# The oldest client this asks for: 0.6.0 deletes a deleted ref's record
# and starts a new ref at the time, and an older client making a branch
# again under a name deleted within the day can have its pushes refused.
deploy/runner-host/README.md+3−3
@@ -169,7 +169,7 @@ rest name [the trusted runner](#the-trusted-runner). In
```sh
KNOTLESS_RUNNER_ARGS="--queue --unmetered did:plc:bcgltzqazw5tb6k2g3ttenbj --trust did:plc:bcgltzqazw5tb6k2g3ttenbj --pull-jobs 4"
KNOTLESS_RUNNER_JOBS=4
KNOTLESS_RUNNER_MEMORY=10
KNOTLESS_RUNNER_MEMORY=12
KNOTLESS_RUNNER_CPUS=4
```
@@ -184,12 +184,12 @@ lets pulls take every job, not half. Its `test` workflow builds every
test binary with coverage and starts PDSes, which takes more than the
default 3 GiB a run: past it the sandbox is killed
(`containerManager.WaitPID failed: EOF` in the log, an OOM kill of
`gvisor_sentry` in `dmesg`). So four jobs of 10 GiB and 4 CPUs each, on a
`gvisor_sentry` in `dmesg`). So four jobs of 12 GiB and 4 CPUs each, on a
dedicated 6-core, 12-thread, 64 GB host (an AX41), which share its threads
only when all four are busy. Within them, cargo would still start a rustc for
each of the host's cores, and knotless-serve's takes more than 3 GiB under
coverage: `harness/cov.mjs` builds as many crates at once as the
cgroup's CPUs, and one for each 4 GiB of its memory at most, so 2 here
cgroup's CPUs, and one for each 4 GiB of its memory at most, so 3 here
(`rustc` killed by `oom-killer` in `dmesg` is this, past those).
knotless names this runner's account first among its `runners`
(`knotless runners knotless://chadtmiller.com/knotless`), so it lands