feat(auto-tuing): add a new auto-tuning system - #879
Open
mingdaw689 wants to merge 1 commit into
Open
Conversation
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.
Summary
src/tuning_manager.h/src/tuning_manager.cc- Manages tuning cache (in-memory + persistent JSON), providesLookup()andRecord()APIs for querying and storing optimal implementations;src/tuning_signature.h- Extracts tuning signatures from operator arguments (tensor shapes, dtypes, scalar parameters) to uniquely identify each configuration;src/config.h- Addedauto_select_flag (default true) toConfigclass, allowing per-call tuning control;src/operator.h- ImplementedResolveConfigOnline<Key>()that benchmarks available implementations on first call and selects the fastest one; injects intoOperator::Call()before operator cache lookup;scripts/generate_wrappers.py- Fixed Python binding logic: only disableauto_select_when user explicitly passesimplementation_indexparameter, preserving auto-tuning for all other cases.Motivation
In the operator library, the same operator can have different underlying implementations. For instance, vendors can provide multiple interfaces, and there are also various algorithms to choose from for handwriting. Therefore, for the same operator, how to select the backend with the best performance in different situations becomes a problem.
Type of Change
feat— new feature / new operator / new platformfix— bug fixperf— performance improvement (no behavioral change)refactor— code restructuring without behavior changetest— adding or fixing tests onlydocs— documentation onlybuild/ci— build system or CI configurationchore— tooling, formatting, or other non-code changes!in the Conventional Commits prefix or aBREAKING CHANGE:footer)Platforms Affected
WITH_CPU)WITH_NVIDIA)WITH_ILUVATAR)WITH_METAX)WITH_CAMBRICON)WITH_MOORE)WITH_ASCEND)WITH_TORCH)Smoke Test Result
Test Results on Supported Platforms
Full `pytest` output (optional)
Benchmark / Performance Impact
Notes for Reviewers