Support for unified recipe registry and user interfaces (#12248) #12319
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
🔗 Helpful Links🧪 See artifacts and rendered test results at hud.pytorch.org/pr/pytorch/executorch/12319
Note: Links to docs will display an error until the docs builds have been completed. ❌ 1 New Failure, 10 Pending, 4 Unrelated FailuresAs of commit 3cf207a with merge base 4e29bc9 ( NEW FAILURE - The following job has failed:
BROKEN TRUNK - The following jobs failed but were present on the merge base:👉 Rebase onto the `viable/strict` branch to avoid these failures
This comment was automatically generated by Dr. CI and updates every 15 minutes. |
facebook-github-bot
added
CLA Signed
Contributor
|
This pull request was exported from Phabricator. Differential Revision: D78034047 |
This PR needs a
|
abhinaykukkadapu
force-pushed
the
export-D78034047
branch
from
bd198d4 to
9dc2249
Compare
Contributor
|
This pull request was exported from Phabricator. Differential Revision: D78034047 |
abhinaykukkadapu
force-pushed
the
export-D78034047
branch
from
9dc2249 to
235433a
Compare
abhinaykukkadapu
added a commit
to abhinaykukkadapu/executorch
that referenced
this pull request
Jul 11, 2025
… (pytorch#12319) Summary: Implements the RFC: pytorch#12248 1. `BackendRecipeProvider` -> Abstract interface that all backends must implement while providing recipes. 1. `recipe_registry` -> Singleton registry that maintains `BackendRecipeProviders` 1. `RecipeType` -> Abstract enum, backends extend this to provide support for specific recipes. 1. `ExportRecipe` will have two class methods a. `get_recipe` -> Queries registry to get recipe w/ specific backend One can simply get and use recipes with: ## Using recipe as-is ``` recipe = ExportRecipe.get_recipe( XNNPackRecipeType.INT8_DYNAMIC_ACT_INT4_WEIGHT_PER_CHANNEL, group_size=32) export(eager_model, example_inputs, dynamic_shapes, recipe) ``` Differential Revision: D78034047
Contributor
|
This pull request was exported from Phabricator. Differential Revision: D78034047 |
abhinaykukkadapu
added a commit
to abhinaykukkadapu/executorch
that referenced
this pull request
Jul 11, 2025
… (pytorch#12319) Summary: Implements the RFC: pytorch#12248 1. `BackendRecipeProvider` -> Abstract interface that all backends must implement while providing recipes. 1. `recipe_registry` -> Singleton registry that maintains `BackendRecipeProviders` 1. `RecipeType` -> Abstract enum, backends extend this to provide support for specific recipes. 1. `ExportRecipe` will have two class methods a. `get_recipe` -> Queries registry to get recipe w/ specific backend One can simply get and use recipes with: ## Using recipe as-is ``` recipe = ExportRecipe.get_recipe( XNNPackRecipeType.INT8_DYNAMIC_ACT_INT4_WEIGHT_PER_CHANNEL, group_size=32) export(eager_model, example_inputs, dynamic_shapes, recipe) ``` Differential Revision: D78034047
abhinaykukkadapu
force-pushed
the
export-D78034047
branch
from
235433a to
1d54036
Compare
abhinaykukkadapu
added a commit
to abhinaykukkadapu/executorch
that referenced
this pull request
Jul 11, 2025
… (pytorch#12319) Summary: Implements the RFC: pytorch#12248 1. `BackendRecipeProvider` -> Abstract interface that all backends must implement while providing recipes. 1. `recipe_registry` -> Singleton registry that maintains `BackendRecipeProviders` 1. `RecipeType` -> Abstract enum, backends extend this to provide support for specific recipes. 1. `ExportRecipe` will have two class methods a. `get_recipe` -> Queries registry to get recipe w/ specific backend One can simply get and use recipes with: ## Using recipe as-is ``` recipe = ExportRecipe.get_recipe( XNNPackRecipeType.INT8_DYNAMIC_ACT_INT4_WEIGHT_PER_CHANNEL, group_size=32) export(eager_model, example_inputs, dynamic_shapes, recipe) ``` Differential Revision: D78034047
abhinaykukkadapu
force-pushed
the
export-D78034047
branch
from
1d54036 to
fd029da
Compare
Contributor
|
This pull request was exported from Phabricator. Differential Revision: D78034047 |
1 similar comment
Contributor
|
This pull request was exported from Phabricator. Differential Revision: D78034047 |
abhinaykukkadapu
added a commit
to abhinaykukkadapu/executorch
that referenced
this pull request
Jul 11, 2025
… (pytorch#12319) Summary: Pull Request resolved: pytorch#12319 Implements the RFC: pytorch#12248 1. `BackendRecipeProvider` -> Abstract interface that all backends must implement while providing recipes. 1. `recipe_registry` -> Singleton registry that maintains `BackendRecipeProviders` 1. `RecipeType` -> Abstract enum, backends extend this to provide support for specific recipes. 1. `ExportRecipe` will have two class methods a. `get_recipe` -> Queries registry to get recipe w/ specific backend One can simply get and use recipes with: ## Using recipe as-is ``` recipe = ExportRecipe.get_recipe( XNNPackRecipeType.INT8_DYNAMIC_ACT_INT4_WEIGHT_PER_CHANNEL, group_size=32) export(eager_model, example_inputs, dynamic_shapes, recipe) ``` Differential Revision: D78034047
abhinaykukkadapu
force-pushed
the
export-D78034047
branch
2 times, most recently
from
748d555 to
9bef6f9
Compare
abhinaykukkadapu
added a commit
to abhinaykukkadapu/executorch
that referenced
this pull request
Jul 11, 2025
… (pytorch#12319) Summary: Implements the RFC: pytorch#12248 1. `BackendRecipeProvider` -> Abstract interface that all backends must implement while providing recipes. 1. `recipe_registry` -> Singleton registry that maintains `BackendRecipeProviders` 1. `RecipeType` -> Abstract enum, backends extend this to provide support for specific recipes. 1. `ExportRecipe` will have two class methods a. `get_recipe` -> Queries registry to get recipe w/ specific backend One can simply get and use recipes with: ## Using recipe as-is ``` recipe = ExportRecipe.get_recipe( XNNPackRecipeType.INT8_DYNAMIC_ACT_INT4_WEIGHT_PER_CHANNEL, group_size=32) export(eager_model, example_inputs, dynamic_shapes, recipe) ``` Reviewed By: kimishpatel Differential Revision: D78034047
abhinaykukkadapu
added a commit
to abhinaykukkadapu/executorch
that referenced
this pull request
Jul 11, 2025
… (pytorch#12319) Summary: Implements the RFC: pytorch#12248 1. `BackendRecipeProvider` -> Abstract interface that all backends must implement while providing recipes. 1. `recipe_registry` -> Singleton registry that maintains `BackendRecipeProviders` 1. `RecipeType` -> Abstract enum, backends extend this to provide support for specific recipes. 1. `ExportRecipe` will have two class methods a. `get_recipe` -> Queries registry to get recipe w/ specific backend One can simply get and use recipes with: ## Using recipe as-is ``` recipe = ExportRecipe.get_recipe( XNNPackRecipeType.INT8_DYNAMIC_ACT_INT4_WEIGHT_PER_CHANNEL, group_size=32) export(eager_model, example_inputs, dynamic_shapes, recipe) ``` Reviewed By: kimishpatel Differential Revision: D78034047
abhinaykukkadapu
force-pushed
the
export-D78034047
branch
from
9bef6f9 to
9c26533
Compare
Contributor
|
This pull request was exported from Phabricator. Differential Revision: D78034047 |
abhinaykukkadapu
added a commit
to abhinaykukkadapu/executorch
that referenced
this pull request
Jul 11, 2025
… (pytorch#12319) Summary: Implements the RFC: pytorch#12248 1. `BackendRecipeProvider` -> Abstract interface that all backends must implement while providing recipes. 1. `recipe_registry` -> Singleton registry that maintains `BackendRecipeProviders` 1. `RecipeType` -> Abstract enum, backends extend this to provide support for specific recipes. 1. `ExportRecipe` will have two class methods a. `get_recipe` -> Queries registry to get recipe w/ specific backend One can simply get and use recipes with: ## Using recipe as-is ``` recipe = ExportRecipe.get_recipe( XNNPackRecipeType.INT8_DYNAMIC_ACT_INT4_WEIGHT_PER_CHANNEL, group_size=32) export(eager_model, example_inputs, dynamic_shapes, recipe) ``` Reviewed By: kimishpatel Differential Revision: D78034047
abhinaykukkadapu
force-pushed
the
export-D78034047
branch
from
9c26533 to
aef15d2
Compare
Contributor
|
This pull request was exported from Phabricator. Differential Revision: D78034047 |
abhinaykukkadapu
added a commit
to abhinaykukkadapu/executorch
that referenced
this pull request
Jul 12, 2025
… (pytorch#12319) Summary: Pull Request resolved: pytorch#12319 Implements the RFC: pytorch#12248 1. `BackendRecipeProvider` -> Abstract interface that all backends must implement while providing recipes. 1. `recipe_registry` -> Singleton registry that maintains `BackendRecipeProviders` 1. `RecipeType` -> Abstract enum, backends extend this to provide support for specific recipes. 1. `ExportRecipe` will have two class methods a. `get_recipe` -> Queries registry to get recipe w/ specific backend One can simply get and use recipes with: ## Using recipe as-is ``` recipe = ExportRecipe.get_recipe( XNNPackRecipeType.INT8_DYNAMIC_ACT_INT4_WEIGHT_PER_CHANNEL, group_size=32) export(eager_model, example_inputs, dynamic_shapes, recipe) ``` Reviewed By: kimishpatel Differential Revision: D78034047
abhinaykukkadapu
force-pushed
the
export-D78034047
branch
2 times, most recently
from
ecd11d3 to
0d7371b
Compare
abhinaykukkadapu
added a commit
to abhinaykukkadapu/executorch
that referenced
this pull request
Jul 12, 2025
… (pytorch#12319) Summary: Pull Request resolved: pytorch#12319 Implements the RFC: pytorch#12248 1. `BackendRecipeProvider` -> Abstract interface that all backends must implement while providing recipes. 1. `recipe_registry` -> Singleton registry that maintains `BackendRecipeProviders` 1. `RecipeType` -> Abstract enum, backends extend this to provide support for specific recipes. 1. `ExportRecipe` will have two class methods a. `get_recipe` -> Queries registry to get recipe w/ specific backend One can simply get and use recipes with: ## Using recipe as-is ``` recipe = ExportRecipe.get_recipe( XNNPackRecipeType.INT8_DYNAMIC_ACT_INT4_WEIGHT_PER_CHANNEL, group_size=32) export(eager_model, example_inputs, dynamic_shapes, recipe) ``` Reviewed By: kimishpatel Differential Revision: D78034047
kimishpatel
approved these changes
Jul 12, 2025
… (pytorch#12319) Summary: Pull Request resolved: pytorch#12319 Implements the RFC: pytorch#12248 1. `BackendRecipeProvider` -> Abstract interface that all backends must implement while providing recipes. 1. `recipe_registry` -> Singleton registry that maintains `BackendRecipeProviders` 1. `RecipeType` -> Abstract enum, backends extend this to provide support for specific recipes. 1. `ExportRecipe` will have two class methods a. `get_recipe` -> Queries registry to get recipe w/ specific backend One can simply get and use recipes with: ## Using recipe as-is ``` recipe = ExportRecipe.get_recipe( XNNPackRecipeType.INT8_DYNAMIC_ACT_INT4_WEIGHT_PER_CHANNEL, group_size=32) export(eager_model, example_inputs, dynamic_shapes, recipe) ``` Reviewed By: kimishpatel Differential Revision: D78034047
abhinaykukkadapu
force-pushed
the
export-D78034047
branch
from
0d7371b to
3cf207a
Compare
Contributor
|
@abhinaykukkadapu has imported this pull request. If you are a Meta employee, you can view this in D78034047. |
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.
Summary:
Implements the RFC: #12248
BackendRecipeProvider-> Abstract interface that all backends must implement while providing recipes.recipe_registry-> Singleton registry that maintainsBackendRecipeProvidersRecipeType-> Abstract enum, backends extend this to provide support for specific recipes.ExportRecipewill have two class methodsa.
get_recipe-> Queries registry to get recipe w/ specific backendOne can simply get and use recipes with:
Using recipe as-is
Differential Revision: D78034047