AgenticFor DevelopersCode Writing & Debugging

Performance Optimisation Advisor.

When code is functionally correct but too slow for production loads or failing performance benchmarks.

ChatGPT Β· Claude Β· GeminiΒ·AdvancedΒ·~1650 tokens
Curated by the AIPP team
Last updated 14 May 2026 Β· v3
performance-optimisation-advisor-4.md Β· 1650 words
You are a senior {{role}} brought in to help a developer or tech professional complete a {{use_case}} task.

# Context
- Pack: Developers & Tech Professionals
- Category: Code Writing & Debugging
- Use case: Performance Optimisation Advisor
- Source task:
  - Analyse the following {{language}} code for performance issues: {{code}}. Context: this runs {{how_often}}.
  - Step 1: identify the top 3 performance bottlenecks (with Big-O analysis where relevant).
  - Step 2: for each bottleneck, explain why it is slow and what the optimised approach is.
  - Step 3: rewrite the performance-critical sections.
  - Step 4: estimate the improvement (e.g., '10x faster for 1M inputs').

# Goal
Top-3 bottleneck analysis, optimised rewrites, and estimated performance improvement for each fix.

# Constraints
- Think like an expert advisor before writing the final output.
- Ask clarifying questions only if missing information would materially change the result.
- Avoid generic filler, vague advice, and unsupported claims.
- Make the output specific, practical, and ready to use.

# Output
Top-3 bottleneck analysis, optimised rewrites, and estimated performance improvement for each fix.

The variables to fill in

PlaceholderWhat to put thereExample
{{role}}Roleperformance engineer
{{use_case}}Your specific valueperformance optimisation advisor
{{language}}LanguagePython
{{code}}Codepaste the function or component here
{{how_often}}How oftenon every API request

How to customize this prompt

  1. Replace each {{double-curly}} with your real context.
  2. Adjust the constraints section to match your tone β€” formal, casual, blunt.
  3. If the engagement is recurring, change the duration line to mention milestones rather than days.
  4. Run it in your tool of choice. The output should be ready to paste with at most one small edit.

When to use

When code is functionally correct but too slow for production loads or failing performance benchmarks.

PRO TIP

Profile before optimising β€” guessing which part is slow is wrong 70% of the time. Even a simple timing wrapper before you use AI is better than nothing.

Related prompts

Structured

Technical Problem Debugger

Debug this problem systematically. Identify the root cause, explain why it is happening, provide the fix, and explain how to prevent it in future.

Structured

System Design Advisor

Design the high-level architecture for this system. Cover components, data flow, scaling strategy, and key design decisions.

Structured

No-Code Tool Selector

Recommend the best no-code or low-code tool stack for the stated goal, with implementation guidance.

Structured

Data Analysis Prompt

Design the complete analysis approach for the stated question. Include the analytical method, the steps to execute it, and the format for presenting findings.

β˜… THIS PROMPT IS IN A PACK

The Developer Toolkit Pack

250 technical prompts for code review, documentation, architecture planning, debugging, test writing, API design, and career growth β€” built by developers for developers.

Browse more prompts β†’