Benchmark Video Search

Instructions

Follow the routing table, then the numbered steps. Execute each step in order on a first run; for a repeat run against an already-indexed deployment run Step 3, then go to Step 5. Reference material is in references/, the runner is in scripts/.

Purpose

Answers two questions about a search profile deployment: does retrieval find the right footage, and where does a query's time go. It drives the vss CLI, the same path the product uses, since the agent adapter shells out to vss search run <mode> --raw for every search, so the numbers describe what ships rather than a REST endpoint that is being retired.

Searches go through vss. To know when ingestion is done and when a wipe has finished, the runner also reads Elasticsearch and RT-CV's stream list directly, read-only, through the deployment's :7777 ingress (derived from --endpoint). It never writes to either. It changes deployment state only through the agent API: it deletes file sources and uploads videos.

When not to use this skill

• For a single video-search question, use vss-search-archive.
• For an end-to-end benchmark of the OpenClaw chat route, this runner does not measure that path; do not present CLI timings as chat timings.
• For a historical benchmark of the retired agent REST search endpoint, use the external legacy run_eval.py noted in references/troubleshooting.md.

Routing