[autotuner] Add benchmark_batch as unified entry point for autotuner benchmarking#1810
Merged
Conversation
fulvius31
reviewed
Mar 24, 2026
jansel
approved these changes
Mar 26, 2026
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
3 participants
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.
Motivation
The
base_search.pyfile is both very frequently modified and getting bigger and bigger by the day. This is a first set of changes intended to both standardize some of the steps and attempt to make things more isolated and decoupled.for this first one, all search algorithms need to compile and benchmark configs, but they entered the pipeline through different methods (parallel_benchmark, parallel_benchmark_population, parallel_benchmark_flat). There was no single public entry point, and metrics were updated as side effects inside benchmark_function, making it hard to reason about where state changes happen.
I intend to make a couple of these as long as we agree it's beneficial, but for now I want to keep these somewhat minimal and incremental. Hopefully this will make expanding autotuning capabilities less error prone and simple in the future.