Skip to main content
CodingArchitectureadvanced

System Performance Bottleneck & Latency Waterfall Profiler

Diagnose CPU spikes, memory leaks, event loop delays, and distributed latency waterfalls in production.

Compatibility & Specs

Compatible AI Models
ClaudeChatGPTGemini
Last UpdatedOct 3, 2026
Customizable Variables3 parameters

How to Use This Prompt

Follow this 3-step workflow to extract high-signal responses from any compatible AI model.

01

1. Tailor the Parameters

Use the interactive customizer above to substitute the bracketed placeholders with your exact context, requirements, and constraints.

02

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.

03

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.

PlaceholderParameter NameTypeStatusDescription & Guidance
[system_runtime]Service Architecture & RuntimetextRequiredLanguage, framework, and deployment contextDefault: Node.js 20 API on AWS ECS with PostgreSQL and Redis, handling JSON payload exports.
[observed_symptoms]Observed SymptomstextareaRequiredLatency 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 DatatextareaRequiredTrace 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.

Sample VariablesInputs
[system_runtime]
Node.js 20 API on AWS ECS with PostgreSQL and Redis, handling JSON payload exports.
[observed_symptoms]
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]
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.
Expected AI ResponseVerified Result
### Performance Bottleneck Analysis #### 1. Classification: CPU-Bound Main Thread Starvation Node.js is single-threaded. Serializing 80,000 objects via `JSON.stringify` synchronously locks the JavaScript event loop for 450ms. During this window, Node cannot process HTTP I/O or respond to ALB health-checks, triggering false-positive ECS task termination. #### 2. The 3-Step Remediation Plan - **Immediate Code Fix (Transform Stream):** Replace in-memory array accumulation with Node.js stream pipeline: ```typescript import { pipeline } from 'node:stream/promises'; // Stream directly from Postgres cursor -> JSON Transform Stream -> HTTP Response ``` This buffers only 16KB in memory at any moment, dropping event loop lag from 500ms to <2ms. - **Offload Heavy Work to Worker Threads:** If data manipulation requires complex calculations, delegate to a Node.js `worker_threads` pool. - **Background S3 Presigned URL Pattern:** For exports exceeding 10,000 rows, convert the endpoint into an asynchronous job: generate the export in a worker, upload to S3, and email the user a download link.

Best Use Cases

Scenarios and roles where this prompt produces maximum leverage.

Backend developers eliminating CPU spikes and event loop blocks under high concurrency
Engineers optimizing slow API responses using APM flamegraph telemetry
Architects restructuring synchronous blocking endpoints into asynchronous streaming architectures

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

View all collections

Related AI Prompts

Complementary workflows in Coding

View all Coding prompts
Codingadvanced

OWASP Security Vulnerability & Dependency Auditor

Inspect code modules for injection vulnerabilities, insecure deserialization, broken access controls, and auth flaws.

claudechatgptgemini
#security-audit#owasp#vulnerability-scanning
Codingadvanced

Relational & NoSQL Database Schema & Indexing Audit

Audit database tables, composite indexes, foreign keys, partition strategies, and N+1 query vulnerability points.

claudechatgptgemini
#database-schema#sql-optimization#indexing
Codingadvanced

Production Bug Forensic Root-Cause Analysis & 5-Whys

Conduct a blameless post-mortem, trace crash telemetry, and execute a 5-Whys root cause investigation.

claudechatgptgemini
#root-cause-analysis#post-mortem#debugging

Related Engineering Guides

Deep-dive playbooks and system prompt methodologies for Coding

View all guides