Files
mtusi2026lab2/evidence/load.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

67 lines
4.1 KiB
Plaintext
Raw Blame History

This file contains ambiguous Unicode characters
This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.
date: 2026-10-30T04:43:19Z commit: 81dd816
# закрытый контур tests/load.py: 64 потока, 8 с, все записи прогона в один чат, 3 повтора с паузой 15 с.
# Клиент — одноразовый контейнер в сети edge стенда (как k6 в лабе 3): 2 CPU, 512 MiB, образ python API по digest,
# tests/, contracts/ и lab.json только для чтения, tcp_tw_reuse=1; адрес — http://lb:8080. С хоста macOS тот же
# прогон упирается в эфемерные порты прокси Docker Desktop (новое соединение на запрос): ~16 000 сокетов TIME_WAIT,
# клиентские ошибки соединения без единого запроса к LB, поэтому замер с хоста не годится.
# На 4-й секунде — docker stats; после прогона — статусы request.handled реплик за окно прогона.
$ docker ps --format '{{.Names}}' | grep -v mtusi2026lab4 # чужие контейнеры на VM во время серии
mtusi-lab6-test-rabbitmq-44e4f19b
$ client() { docker run --rm --network mtusi2026lab4_edge --cpus 2 --memory 512m --sysctl net.ipv4.tcp_tw_reuse=1 -v tests,contracts,lab.json:ro -v evidence/load:/out python:3.14-slim-trixie@sha256:51dafde8… python /w/tests/load.py "$@"; }
$ client --base-url http://lb:8080 --duration 8 --concurrency 64 --output /out/run1.json
exit 0
{'elapsed_seconds': 8.191, 'successful_requests': 17199, 'failed_requests': 0, 'successful_rps': 2099.764, 'successful_latency_ms': {'p50': 25.927, 'p95': 68.522, 'p99': 96.55}}
$ docker stats --no-stream (середина прогона): контейнер CPU% память
api-1 89.46% 215MiB / 512MiB
api-2 91.69% 214.8MiB / 512MiB
lab4-load-client 106.19% 83.36MiB / 512MiB
lb-1 80.99% 25.83MiB / 128MiB
postgres-1 215.44% 164.6MiB / 1GiB
s3-1 0.81% 327.6MiB / 512MiB
valkey-1 6.12% 14.06MiB / 128MiB
$ docker compose logs --since 2026-10-30T04:43:19Z api | request.handled: статус метод маршрут число
200 GET /health/live 1
200 GET /health/ready 23
201 POST /api/v1/auth/sessions 3
201 POST /api/v1/chats 1
201 POST /api/v1/chats/{chat_id}/messages 17199
201 POST /api/v1/users 3
$ client --base-url http://lb:8080 --duration 8 --concurrency 64 --output /out/run2.json
exit 0
{'elapsed_seconds': 8.207, 'successful_requests': 17386, 'failed_requests': 0, 'successful_rps': 2118.439, 'successful_latency_ms': {'p50': 26.371, 'p95': 66.641, 'p99': 86.248}}
$ docker stats --no-stream (середина прогона): контейнер CPU% память
api-1 92.83% 216.9MiB / 512MiB
api-2 93.26% 216.8MiB / 512MiB
lab4-load-client 106.22% 82.68MiB / 512MiB
lb-1 79.14% 26.29MiB / 128MiB
postgres-1 213.30% 174.1MiB / 1GiB
s3-1 0.01% 337.3MiB / 512MiB
valkey-1 6.36% 13.95MiB / 128MiB
$ docker compose logs --since 2026-10-30T04:43:43Z api | request.handled: статус метод маршрут число
200 GET /health/live 1
200 GET /health/ready 23
201 POST /api/v1/auth/sessions 3
201 POST /api/v1/chats 1
201 POST /api/v1/chats/{chat_id}/messages 17386
201 POST /api/v1/users 3
$ client --base-url http://lb:8080 --duration 8 --concurrency 64 --output /out/run3.json
exit 0
{'elapsed_seconds': 8.229, 'successful_requests': 17332, 'failed_requests': 0, 'successful_rps': 2106.215, 'successful_latency_ms': {'p50': 26.607, 'p95': 67.007, 'p99': 88.37}}
$ docker stats --no-stream (середина прогона): контейнер CPU% память
api-1 96.95% 217.1MiB / 512MiB
api-2 97.50% 218.4MiB / 512MiB
lab4-load-client 101.96% 82.94MiB / 512MiB
lb-1 79.73% 26.28MiB / 128MiB
postgres-1 212.83% 186.4MiB / 1GiB
s3-1 3.74% 343MiB / 512MiB
valkey-1 6.35% 13.94MiB / 128MiB
$ docker compose logs --since 2026-10-30T04:44:07Z api | request.handled: статус метод маршрут число
200 GET /health/live 1
200 GET /health/ready 23
201 POST /api/v1/auth/sessions 3
201 POST /api/v1/chats 1
201 POST /api/v1/chats/{chat_id}/messages 17332
201 POST /api/v1/users 3
$ docker compose exec -T postgres psql: сообщений в базе после серии
70839