forked from mtusi2026/mtusi2026lab2
One to eight replicas of 1 CPU, 512 MiB and one worker each, three repeats per rate; the 4x1 point comes from series A. Peak successful RPS: 1 720 for one replica, 2 936 for two, 4 724 for four and only 4 260 for eight, lower than four. Up to two replicas the API is the limit (101 % and 201 % of its CPU). At eight replicas the API uses 473 of its 800 % and the balancer 40 % of a core, while PostgreSQL is at 178 of 200 %, 47.5 of the 64 pool connections wait for a chat row lock and the balancer queue holds 744 requests. The locking SELECT ... FOR UPDATE of the chat takes 14.2 ms on average, 97 % of all statement time of the step, and about 7 connections sit idle in transaction: the lock holders wait for the application between round trips. A universal scalability law fit over 1, 2, 4 and 8 CPUs gives sigma 0.014 and kappa 0.038, a peak near five replicas and a decline after it. No step of this series was rejected as disturbed. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01V1d3RLHNBBMA6UqBLLJv27
Доказательства
Храните небольшие обезличенные результаты: команды и stdout проверок, JSON/CSV агрегатов нагрузки, EXPLAIN, dashboard JSON, текст разбора отказа. Укажите дату, commit, аппаратные лимиты и профиль нагрузки.
Не добавляйте .env, session tokens, cookies, приватные ключи, credentials, реальные сообщения, raw dumps и signed URLs. Для скриншотов скрывайте секреты. Большие логи/бинарные traces сохраняйте отдельно по правилам преподавателя; одного скриншота без методики недостаточно.