Add API benchmark suite#55
Open
vornicx wants to merge 1 commit into
Open
Conversation
14 tasks
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.
Closes #30.
Summary
/benchmarks./apiroute plus/healthas a baseline, including auth-protected admin metrics and multipart uploads..env.benchmark.example, persisted JSON/Markdown reports, and a CI smoke benchmark gate.Validation
npm testnpm run benchmark:smokenpm run benchmarkLatest full local run: 21 endpoints, 525 requests, 0% error rate, gate passed, worst p99 26.61ms (
GET /health).Notes
Local benchmark mode can bypass API rate limiting so endpoint behavior is measured rather than limiter behavior. Staging/production runs can set
BENCHMARK_TARGET_HOSTandBENCHMARK_AUTH_TOKENinstead.Benchmark Environment
Hardware
127.0.0.1, local ephemeral API server)Runtime
If submitted by or with an AI agent
npm installinitially hit a Prisma postinstall network reset, then dependencies were repaired withnpm install --ignore-scripts; the benchmark itself does not depend on Prisma engines