Files
mtusi2026lab4/evidence/limits.txt
T
ArtyomandClaude Opus 5.5 c8cb263c77 Retake the lab 4 evidence on the final code and finish the report
The level 3 and 4 evidence was taken on 24f9d61 and a774a2f, before the
lab 3 fixes were carried over and before the reconciler. Take all of it
again in one series on 81dd816, whose application and stand code is the
final one: a fresh clone runs the launch block of the report from secrets
to reset-data, then one stand from clean volumes gives the smoke, stack,
limits, lb-check, failover of each replica and of the upload replica,
persistence, S3 outage, S3 privacy, lost-answer retry, upload faults, all
stack checks, storage layout and three runs of the upload memory matrix.

The three memory runs keep the peak with three slots at 297-345 MiB
against 512 MiB at the limit without them, but at 40 uploads of 10 MiB
the wait for a slot nears the 8 s request timeout and one run of three
gave 7 of 80 a 503. Those timeouts left 67 invisible intents; the record
shows the reconciler seeing them as fresh and the sweep removing all of
them after the grace period.

Message write load is taken with tests/load.py from a container on the
edge network: 2 106 RPS, no errors, replicas and PostgreSQL at their CPU
limits. The first try from the macOS host is kept as a discarded attempt,
it ran out of ephemeral ports while the replicas answered every request.

The report gets the defense answers, the load section, the evidence
commits, the upload limit order as the pipeline applies it, medians in
the track 2 cost table and the proposals over the word limit; the evidence
index lists every file with its command and commit.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01V1d3RLHNBBMA6UqBLLJv27
2026-10-30 07:55:34 +03:00

27 lines
2.7 KiB
Plaintext

date: 2026-10-30T04:29:07Z commit: 81dd816
$ docker compose --profile bench --profile tools --profile reconcile config --format json (declared)
service cpus/mem ports secrets volumes networks ro
---------- ---------- ------------------------------- -------------------------------------------------------------------------- ---------- ---------------------- -----
api 1/512MiB - cache_url,cursor_secret,database_url,s3_access_key_id,s3_secret_access_key - backend(internal) true
k6 2/512MiB - - - edge false
lb 1/128MiB 127.0.0.1:18084,127.0.0.1:24084 - - backend(internal),edge true
migrate 0.5/256MiB - database_url - backend(internal) false
postgres 2/1024MiB - postgres_password pgdata backend(internal) false
reconciler 1/256MiB - database_url,s3_access_key_id,s3_secret_access_key - backend(internal) true
s3 1/512MiB - s3_root_password,s3_root_user s3data backend(internal) true
s3-cli 0.5/64MiB - s3_access_key_id,s3_root_password,s3_root_user,s3_secret_access_key - backend(internal) true
s3-init 0.5/64MiB - s3_access_key_id,s3_root_password,s3_root_user,s3_secret_access_key - backend(internal) true
valkey 0.5/128MiB - valkey.conf valkeydata backend(internal) false
$ docker inspect (running containers: hostname = X-Instance-Id, applied limits)
service hostname cpus memory published
-------- ------------ ---- ------- ---------------------------------------------------
api 0cc3ee358e59 1 512MiB
api 899a952a5a21 1 512MiB
lb a51c65de79e9 1 128MiB 127.0.0.1:18084->8080/tcp,127.0.0.1:24084->8404/tcp
postgres 54d604398b41 2 1024MiB
s3 89f363c93892 1 512MiB
valkey 99365a2af315 0.5 128MiB
PASS: limits, ports, secrets, volumes and networks match the policy