performance-and-visualization
Benchmark LightGlue latency and throughput, and create or save match, keypoint, pruning, and benchmark plots.
- License 许可
- Apache-2.0
- 最近更新
- 2026-09-03
- Stars
- ★ 351
- Forks
- 27
01 前言 Front Matter
- name
- performance-and-visualization
- license
- Apache 2.0
- metadata
- { "disco-role": "operating" }
- description
- Benchmark LightGlue latency and throughput, and create or save match, keypoint, pruning, and benchmark plots.
- disable-model-invocation
- true
02 资源文件 4
- 参考文档references/benchmarking.md5.2 KB
- 参考文档references/troubleshooting.md3.4 KB
- 参考文档references/visualization.md2.8 KB
- 脚本scripts/benchmark_lightglue.py17.8 KB
03 SKILL.md 正文
Performance and Visualization
Use this sub-skill when the task is about measuring LightGlue speed or making match visualizations.
Primary entry points
scripts/benchmark_lightglue.py: benchmark matcher latency or throughput with safe defaults, optional compile and FlashAttention toggles, pruning-threshold overrides, a synthetic fallback image pair, and--save/--no-showsupport.references/benchmarking.md: benchmark workflow, measurement semantics, speed knobs, and weight-download caveats.references/visualization.md:viz2dplotting helpers for matches, keypoints, pruning colors, labels, and saved plots.references/troubleshooting.md: common device, backend, compile, pruning, and headless display fixes.
Boundaries
- For matcher constructor choices, confidence settings, and routing around
LightGlue configuration, use
../matcher-configuration/SKILL.md. - For extractor selection and feature-specific setup, use
../extractors-and-features/SKILL.md. - For a one-off image-pair matching workflow rather than benchmarking or
plotting, use
../image-pair-matching/SKILL.md.
Notes
- The benchmark script times matcher forward passes after feature extraction.
- First-use runs may download pretrained extractor or matcher weights.
- Runtime dependencies assumed here are
torch,torchvision,numpy,opencv-python,matplotlib, andkornia.
04 同仓库更多 Skills
passnet-triton-opt
Make a single PassNet Triton kernel fast AND numerically faithful: performance model (when a replacement can win at all), block/grid/warp tuning, autotune policy, launch overhead, and per-op numeric recipes to pass the dtype baseline tolerances. Use when a pass matches and is correct but speedup below expected, or when correctness fails by small numeric margins.
passnet-solve
END-TO-END playbook for solving one PassNet sample: analyze the computation graphs, decide the optimization strategy (what to fuse, what to replace, what to leave alone), drive the iteration loop, and maximize the sample score. This is the ENTRY skill — invoke it first for any PassNet optimization task; it tells you when to use passnet-pattern-fusion, passnet-triton-opt and passnet-feedback.
passnet-skill
PassNet GPU kernel optimization via compiler passes. Design and implement Triton-based optimization passes, create pass files under ./pass_dir/, self-evaluate with pass_evaluator, and iterate to maximize GPU speedup.
passnet-pattern-fusion
Author PassNet pass files: write patterns that actually MATCH the FX graph, pick fusion regions (which ops to absorb into one Triton kernel), and structure multi-pass submissions with the mandatory shared-dispatch architecture. Use when creating or fixing pattern()/replacement_args()/replacement_func() files, when a pass "failed to match", or when deciding how to fuse multiple kernels/ops.
passnet-orchestrate
Round/batch planning and decision support for PassNet graph optimization. Use for multi-sample triage, worker allocation, eval-budget policy, and post-eval keep/revert decisions. For solving one concrete sample end to end, use passnet-solve as the entry skill; consult this skill only when you need broader planning or a specific decision gate.
passnet-feedback
Fast, deterministic feedback for PassNet work: pre-flight pattern/match verification WITHOUT burning a GPU evaluation, per-node bottleneck analysis of a sample's graphs, and eval-log parsing into per-variant status + estimated score + failure classification. Use BEFORE every GPU evaluation (check_pattern), at the START of a sample (analyze_graph), and AFTER every evaluation (parse_eval_log).