Correspondence-scaling timing benchmark + group timing scripts under scripts/timing/#634
Merged
Conversation
…er scripts/timing/ Introduces experimental/overhead_matching/swag/scripts/timing/ as the home for pipeline timing benchmarks, so they aren't scattered in the scripts/ catch-all. - Moves measure_pipeline_latency.py (from #632) into scripts/timing/. - Adds the local-LLM correspondence timing benchmark: correspondence_scaling_common.py (stockpile/query loading, match prompt, JSON validation, extrapolation/report) and benchmark_correspondence_scaling_ollama.py (gemma3:27b sweep via ollama), plus a README with setup + reproduction. - Adds scripts/timing/BUILD with the three targets; removes the measure_pipeline_latency target from scripts/BUILD and widens evaluate_histogram_on_paths visibility so the relocated target can depend on it. Backs the paper's timing numbers: pipeline ~36.6 s/observation, and the LLM alternative ~5.4/7.6 min per panorama (Gemma 3 27B, no/with thinking).
1ced5ff to
39748c2
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Stacked on #632.
What
experimental/overhead_matching/swag/scripts/timing/as the home for pipeline timing benchmarks, so they don't accumulate in thescripts/catch-all. Movesmeasure_pipeline_latency.py(from Add a script to measure latency #632) into it.Files (in
scripts/timing/)measure_pipeline_latency.py— moved fromscripts/(unchanged).correspondence_scaling_common.py— loads the Chicago OSM stockpile (28,582 unique tag bundles) + panorama query landmarks, builds the match prompt, validates JSON output, extrapolates per-call timings to per-landmark / per-panorama / full-city cost.benchmark_correspondence_scaling_ollama.py—gemma3:27bsweep via ollama (candidate-fill × query-batch × thinking on/off).correspondence_scaling_README.md— setup + reproduction.BUILD— the three targets.scripts/BUILD: drops themeasure_pipeline_latencytarget (moved) and widensevaluate_histogram_on_pathsvisibility so the relocated target can depend on it.Result (backs the paper)
Notes
gemma3:27bpulled on first run) and VIGOR/pano_v2 data under/data/overhead_matching/datasets/— not CI-reproducible; commands in the README./data/overhead_matching/evaluation/timing/.scripts/timing/).