Repository navigation
test(perf): scripted load test and performance workflow - #592
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds a bounded hosted-dev HTTP load test and a manual performance workflow for the course performance/scalability demonstration. The runner reuses three authenticated sessions, ramps through 1/10/25/50/100 VUs with three-minute steady windows, drives read-heavy group/chat/Archive journeys, and caps photo contributions at three tiny files. It retains per-request JSON and p50/p95/p99, throughput, and error summaries; each steady stage must meet p95 < 2 seconds and errors < 1%.
The workflow accepts
target_urlandmax_vus, uses SHA-pinned actions, read-only repository permissions and an artifact upload that runs on failure. A Python analyzer creates measured/projected tables and three 1280×720 presentation charts. Empty collecting-state archives are counted separately from issued media capabilities. A separate confirmation mode reuses private fixtures, runs only the maximum-VU stage and performs reads without account creation, uploads or chat writes.Hosted evidence: the original 16-minute mixed-workload run passed through 50 VUs. At 100 VUs, p95 was 1,368 ms but errors were 10.88%, so the result is FAIL. All 339 failures fell within the installation step of dev deployment 40341542790. The failed run is retained. A separate three-minute post-deployment read-only 100-VU confirmation passed with p95 625 ms and zero errors. Capacity projections are labelled as incident-influenced and do not establish physical host saturation. Presentation artifacts were delivered separately.
Validation:
npm ci,npm run test:root,npm run test:fast, focused harness regression, Prettier and ESLint, and the full pre-push checks. The analyzer recovered known parameters in a synthetic numerical check; all three final PNGs are 1280×720, and JSON evidence was scanned for session-token leakage.No merge or deployment is requested.