Skip to content

Library-specific CPU advice; README for run's new features - #17

Merged
thelastbackspace merged 2 commits into
mainfrom
feat/cpu-advice
Nov 6, 2026
Merged

thelastbackspace merged 2 commits into
mainfrom
feat/cpu-advice

Conversation

@thelastbackspace

Copy link
Copy Markdown
Owner
  • The CPU-cost finding matches its hottest functions (≥10% of CPU) against known library costs: Mongoose, TypeORM, Sequelize, Prisma, Express's per-response ETag, class-transformer/validator, large JSON, password hashing, logging, GC. From the NestJS + TypeORM run: 26% Express res.send, ~40% TypeORM query building.
  • README: -H, --probe, the CPU-cost and failed-response findings, mysql.
  • Test: the Prometheus histogram test flaked about 1 in 6 full runs (a no-op call measured over 5 ms on a busy machine); bucket margins widened.

@thelastbackspace
thelastbackspace merged commit 1a95413 into main Nov 6, 2026
14 checks passed
@thelastbackspace
thelastbackspace deleted the feat/cpu-advice branch November 6, 2026 20:05
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