René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Add CI benchmark job on POSIX to detect performance regressions","articleBody":"# Motivation\n\n  Code changes have the potential to shift client/server throughput and latency in ways that aren't visible in functional tests. Today we\n   have no automated signal when a change regresses performance, and reviewers don't have a consistent number to reference when\n  evaluating PR impact.\n\n# Proposal\n\n  Add a CI job that:\n\n  1. Runs the existing benchmark/ targets (or a curated subset) on the POSIX build.\n  2. Records the results as a machine-readable artifact (CSV/JSON) attached to the workflow run.\n  3. Either:\n    - (a) Baseline comparison: compares against a stored baseline (main branch numbers) and flags regressions beyond a threshold, or\n    - (b) Historical record: posts results as a PR comment or uploads them to a dashboard so humans can eyeball trends.\n\n  Starting with (b) is likely lower-effort and sufficient for surfacing regressions during review.","author":{"url":"https://github.com/AlexLanzano","@type":"Person","name":"AlexLanzano"},"datePublished":"2026-04-22T12:26:17.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":0},"url":"https://github.com/342/wolfHSM/issues/342"}