performance-debug

Diagnose training slowdowns and bottlenecks in quantum-aware PyTorch/PennyLane pipelines.

Updated Jun 17, 2025
One-click install
npx skills add https://github.com/necatiincekara/Quanvolutional-Neural-Network --skill performance-debug-necatiincekara
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: performance-debug
Source: https://github.com/necatiincekara/Quanvolutional-Neural-Network/tree/main/.agents/skills/performance-debug
Command: npx skills add https://github.com/necatiincekara/Quanvolutional-Neural-Network --skill performance-debug-necatiincekara

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Diagnose training slowdowns, dead quantum signals, and scheduler mistakes in hybrid quantum-classical models.

Core Features & Use Cases

  • Identify bottlenecks across the training path, from JIT compilation cost to quantum circuit throughput.
  • Distinguish failure modes such as slow first epoch, persistent slowness, non-decreasing loss, and unstable accuracy; provide targeted fixes.
  • Provide actionable guidance on reruns or ablations to validate hypotheses.

Quick Start

Run the performance-debug workflow on the current training loop to identify bottlenecks and propose fixes.

Frequently Asked Questions about performance-debug

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I debug training slowdowns in hybrid quantum-classical PyTorch models?

Debug training slowdowns in hybrid quantum-classical PyTorch models by diagnosing first-epoch JIT compilation costs, gradient stability, and quantum-layer throughput to identify observable bottlenecks and propose minimal fixes. It analyzes your PennyLane pipeline to pinpoint performance degradation points.

Why does my PennyLane quantum layer cause persistent slowness across all epochs?

Persistent slowness across all epochs is distinguished from first-epoch JIT costs by analyzing quantum circuit throughput and scheduler mistakes. The workflow identifies whether the bottleneck stems from quantum-layer execution overhead or suboptimal training loop configuration.

What causes dead quantum signals and non-decreasing loss in hybrid quantum nets?

Dead quantum signals and non-decreasing loss in hybrid quantum nets are caused by gradient instability and scheduler mistakes. The workflow diagnoses these failure modes by evaluating gradient flow through quantum layers and proposing targeted fixes.

Can I use this to diagnose unstable accuracy in a PennyLane training pipeline?

Yes, you can diagnose unstable accuracy in a PennyLane training pipeline by running the workflow. It identifies failure modes like unstable accuracy and non-decreasing loss, then recommends reruns or ablations to validate hypotheses.

What is the best way to identify first-epoch JIT compilation costs in hybrid quantum training?

Identify first-epoch JIT compilation costs in hybrid quantum training by applying diagnostics to the training loop to isolate initial runtime overhead from persistent bottlenecks. The workflow distinguishes slow first epoch failures from other performance issues.

Do I need to run ablations to validate performance fixes in hybrid quantum nets?

You need to run ablations to validate performance fixes in hybrid quantum nets when the diagnosis requires confirming hypotheses about bottlenecks. The workflow recommends reruns or ablations when needed to verify that proposed minimal fixes resolve the issue.