Vss Benchmark Video Summarization

Instructions

Follow the routing table and step-by-step workflow below. Execute each step in order on a first run. For repeat runs, go directly to the Repeat Runs section. Detailed reference material lives in references/ and benchmark scripts live in scripts/.

⚠️ Shared GPU systems: On a multi-user host, multiple LVS instances may be running on different ports. Always benchmark against the instance YOU deployed. Never assume port 38111, always use the exact endpoint URL returned by vss-build-vision-ai when you deployed LVS. If you did not deploy an LVS instance in this session, deploy one first before running benchmarks.

Purpose

Measure the latency and throughput limits of a deployed LVS (Long Video Summarization) instance, identify GPU and pipeline bottlenecks, and suggest configuration changes that improve performance. Produces XLSX reports and JSON result files per scenario, plus a natural-language analysis with improvement recommendations.

Do NOT use this skill for:

• Deploying LVS, use the vss-build-vision-ai skill with the lvs profile.
• Production monitoring or alerting, this is an offline benchmarking tool.
• Non-LVS VSS profiles (RTVI, search-only, etc.), the /files API and /summarize endpoint are LVS-specific.

When to Use

• Measure single-file latency or burst throughput of a deployed LVS instance
• Identify whether the VLM or LLM stage is the pipeline bottleneck
• Get concrete config recommendations (chunk size, frame count, resolution, concurrency) after a benchmark run
• Compare performance across hardware profiles or config changes on the same LVS deployment
• Re-run a benchmark scenario after setup is already complete (see Repeat Runs)

Routing