Define realistic traffic, workload data, measurements and stopping rules for an authorized performance test.
No public result for version 1 yet
Version 1 · 3 variables · 3 required
Fill in the values below — the customized prompt updates as you type. marks a required value.
The system and representative actions. Default: A project API: list projects, open project details, and create a task.
Observed volume and clearly labeled target metrics. Default: Observed peak is about 40 requests/second, 90% reads. Proposed goal: read p95 below 400 ms with errors below 1%.
Authorized target, dependencies, operational limits and cleanup needs. Default: Isolated staging environment with synthetic accounts. External email is disabled. Stop if database CPU stays above 85% for two minutes.
Plan a load test for the authorized environment described below.
System and user journeys: A project API: list projects, open project details, and create a task.
Traffic model and performance goals: Observed peak is about 40 requests/second, 90% reads. Proposed goal: read p95 below 400 ms with errors below 1%.
Environment, dependencies and limits: Isolated staging environment with synthetic accounts. External email is disabled. Stop if database CPU stays above 85% for two minutes.
Specify the workload mix, arrival pattern, data distribution, ramp-up, steady-state period and recovery observation. Keep these choices tied to the supplied traffic model; flag estimates that need validation.
List client and server measurements, including latency percentiles, errors, throughput and saturation indicators relevant to this system. Identify how test data, caching, external dependencies and the load generator itself could distort results.
Give explicit start prerequisites, stop conditions, cleanup and comparison criteria for a later repeat run. Separate a proposed threshold from a contractual target. Do not execute traffic, invent capacity numbers, or claim the system passes before measurements exist.No public examples yet for version 1
Curated prompt only. No example output or model test is attached; model compatibility has not been verified. Default inputs are illustrative practice material; replace them with your own facts and context.
Reports go to moderators and are never shown publicly.
No public results yet
Break a dependency replacement into reviewable stages with compatibility checks, exit criteria and realistic rollback limits.
No public results yet
Find source-visible labeling, semantics and keyboard risks, while separating code findings from checks that require a browser.
No public results yet
Map feature assets, trust boundaries and data flows to concrete threats, existing controls and targeted verification tasks.
No public results yet
Turn an API contract into a small client design that handles retryable failures, deadlines and idempotency deliberately.
No public results yet
Interpret supplied plan evidence and prioritize query or index experiments without inventing costs or speedups.
No public results yet
Check whether keys, constraints and relationships actually enforce the application's stated data rules.
Oldest first · one level of replies
Sign in to join the discussion. Share what you learned or made with this prompt.
No comments yet
Be the first to share how this prompt worked for you.