PromptVaultBenchmark harness with setup kept out of timing
For developers needing a runnable microbenchmark around the function open in their editor.
Works with
- Codex
- GitHub Copilot
The prompt55 words · 2 blanks
What you fill in
- Benchmark tool
[benchmark_tool]ExampleGo testing.B - Maximum file length
[line_limit]Example80
How to use it
- 1Open it in PromptVault. Find it in Coding, or search for “Benchmark harness with setup kept out of timing”.
- 2Fill in the 2 blanks. benchmark tool and maximum file length — the only things the prompt cannot know.
- 3Copy and paste it into GitHub Copilot. It also works with Codex.
About this prompt
“Benchmark harness with setup kept out of timing” is a beginner coding prompt. For developers needing a runnable microbenchmark around the function open in their editor. It is 55 words long and written to get a usable answer on the first message, in Codex and GitHub Copilot or any other chat assistant. Good for: performance, testing, automation and first draft. Like every prompt in PromptVault, it was written and edited in-house, and it works offline once the app is installed.
More coding prompts
All 120 in Coding
A load test that fails on latency and error regressionsFor engineers checking an endpoint under pressure; returns one runnable repository-native script.- Add a bounded worker pool without hidden queue growthFor engineers adding concurrency safely; returns implementation code and focused tests.
- An executable test suite from a behavior briefFor engineers turning expected behavior into focused unit tests.
- Fault injection for an outbound HTTP boundaryFor engineers adding repeatable transport failures without making tests depend on the network.
- Hardened CI for untrusted pull requestsFor maintainers needing a ready-to-run workflow that limits token and secret exposure.
- Sensitive fields stay out of application logsFor engineers adding a reusable redaction boundary to an existing logging path.