Measure scripts, running processes, or whole systems to find performance bottlenecks. Select suitable tools, add measurement code when needed, and report CPU, GPU, memory, and communication findings with prioritized recommendations and a record of file changes.
- Finding slow functions in a Python script
- Investigating CPU and GPU memory usage
- Measuring communication overhead across multiple GPUs
wanshuiyin/Auto-claude-code-research-in-sleep☆ 17.8KUpdated Oct 19, 2026
Profile a DeepStream pipeline with Nsight Systems and derive its configs from the measurement. Use when the user asks for an efficient, performant, or profiled pipeline — or to benchmark, tune, or measure FPS.
The English summary is being prepared. Showing the original description.
NVIDIA/skills☆ 3.7KUpdated Oct 20, 2026
Diagnose and fix slow pyfixest regression GRIDS (many feols/fepois calls run sequentially) that stay slow despite demeaner_backend="cupy64" and an idle GPU. Use when: (1) a script looping dozens of pf.feols models on a 100k+ row panel takes ~1 min/model, (2) process inspection shows ~1-1.5 cores busy and nvidia-smi shows ~0% GPU utilization with a resident cupy context, (3) planning any worker prompt that will run a model grid (robustness variants x FE structures x domains). Root cause: per-model CPU-side single-threaded fixed costs (formulaic model-matrix build, interaction construction, singleton detection, cluster vcov) dominate wall time; GPU demeaning is a small slice. Fix: shard the model grid across OS processes and/or use pyfixest multiple-estimation syntax; mandate this IN THE WORKER PROMPT.
The English summary is being prepared. Showing the original description.
kennethkhoocy/applied-micro-skills☆ 22Updated Sep 5, 2026