Skip to content

run: probe phase for undistorted per-request findings; failed-response warning - #15

Merged
thelastbackspace merged 1 commit into
mainfrom
feat/probe
Nov 6, 2026
Merged

thelastbackspace merged 1 commit into
mainfrom
feat/probe

Conversation

@thelastbackspace

Copy link
Copy Markdown
Owner

From running traceperf run on lujakob/nestjs-realworld-example-app (NestJS 7, TypeORM, Postgres).

Under concurrent load every await also waits for the saturated event loop, so call times are inflated: four "check this query's plan" findings for 1 ms queries on tiny tables. run now sends --probe requests per path (default 10) one at a time after the warm-up and takes dominant / sequential / N+1 findings from them; blocking, queueing, errors and CPU cost still come from the load.

Also: a first finding when most responses failed (an expired JWT used to produce "no issues found"), and once-in-10+ counts as an outlier.

Re-checked: NestJS (only the real CPU-cost finding left), Mongoose (.lean()), RealWorld, planted apps.

@thelastbackspace
thelastbackspace merged commit 881d45b into main Nov 6, 2026
14 checks passed
@thelastbackspace
thelastbackspace deleted the feat/probe branch November 6, 2026 19:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant