System Performance Bottleneck & Latency Waterfall Profiler
Diagnose CPU spikes, memory leaks, event loop delays, and distributed latency waterfalls in production.
Compatibility & Specs
144 words • 1145 characters
Customize Prompt
Fill in the variables below. Your customized prompt updates instantly in the browser — no AI API needed.
Language, framework, and deployment context
Latency metrics, CPU graphs, memory leaks
Trace data, Datadog flamegraph, or slow function traces
How to Use This Prompt
Follow this 3-step workflow to extract high-signal responses from any compatible AI model.
1. Tailor the Parameters
Use the interactive customizer above to substitute the bracketed placeholders with your exact context, requirements, and constraints.
2. Send to AI Model
Copy the prompt and paste it into Claude, ChatGPT, Gemini, or Copilot. These models follow structured multi-step constraints reliably.
3. Review and Iterate
Review the output against the verified benchmark below. Follow up in the conversation to stress-test edge cases or refine tone.
Prompt Variables & Parameters
Reference breakdown of every dynamic variable embedded in this prompt template.
| Placeholder | Parameter Name | Type | Status | Description & Guidance |
|---|---|---|---|---|
| [system_runtime] | Service Architecture & Runtime | text | Required | Language, framework, and deployment contextDefault: Node.js 20 API on AWS ECS with PostgreSQL and Redis, handling JSON payload exports. |
| [observed_symptoms] | Observed Symptoms | textarea | Required | Latency metrics, CPU graphs, memory leaksDefault: When users request large CSV/JSON report exports, container CPU jumps to 100% and event loop lag exceeds 500ms, causing unrelated lightweight health-check requests to time out and ECS to kill the container. |
| [apm_data] | APM / Profiler Data | textarea | Required | Trace data, Datadog flamegraph, or slow function tracesDefault: Datadog APM flamegraph shows 70% of CPU time spent in `JSON.stringify` and `Array.prototype.map` formatting 80,000 database row objects in memory before sending the HTTP response. |
Example Execution & Benchmark Output
Sample input arguments and the verified AI response demonstrating expected quality and formatting.
Best Use Cases
Scenarios and roles where this prompt produces maximum leverage.
Tips for Best Results
Techniques to elevate response fidelity
- •Provide rich background context rather than one-sentence inputs to receive deep, non-generic responses.
- •Engage in multi-turn conversation: use the initial output as a baseline, then ask the AI to sharpen specific sections.
- •Prompt the model to highlight any hidden assumptions or missing trade-offs in its recommendations.
Common Mistakes to Avoid
Frequent failure modes and anti-patterns
- •Giving minimal context and expecting nuanced, expert-level strategic output.
- •Not validating factual references, citations, or statistical claims with verified primary sources.
- •Skipping the customization step and pasting raw bracketed template variables into the AI chat.
Part of Curated Collections
This prompt is sequenced as part of these goal-oriented workflows
Related AI Prompts
Complementary workflows in Coding
OWASP Security Vulnerability & Dependency Auditor
Inspect code modules for injection vulnerabilities, insecure deserialization, broken access controls, and auth flaws.
Relational & NoSQL Database Schema & Indexing Audit
Audit database tables, composite indexes, foreign keys, partition strategies, and N+1 query vulnerability points.
Production Bug Forensic Root-Cause Analysis & 5-Whys
Conduct a blameless post-mortem, trace crash telemetry, and execute a 5-Whys root cause investigation.
Related Engineering Guides
Deep-dive playbooks and system prompt methodologies for Coding
How to Write Better AI Prompts
A comprehensive playbook for crafting high-fidelity prompts: mastering context, roles, objectives, constraints, output schemas, few-shot examples, and systematic iteration.
AI Prompts for Software Developers
Turn modern LLMs into senior engineering peers: tactical prompt patterns for architecture review, edge-case test generation, root-cause debugging, and technical documentation.