-
Notifications
You must be signed in to change notification settings - Fork 689
[ET-VK] 8/n Split dispatches between multiple command buffers. This diff adds a config to limit the maximum number of command buffers created when splitting execution between multiple command buffers. #13113
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[ET-VK] 8/n Split dispatches between multiple command buffers. This diff adds a config to limit the maximum number of command buffers created when splitting execution between multiple command buffers. #13113
Conversation
…iff adds a config to limit the maximum number of command buffers created when splitting execution between multiple command buffers. This diff introduces a new configuration option, `execute_max_cmds`, to limit the maximum number of command buffers created when splitting execution between multiple command buffers. This feature allows for more efficient management of command buffers, particularly in scenarios where the number of nodes in the graph is large. Differential Revision: [D79575908](https://our.internmc.facebook.com/intern/diff/D79575908/) [ghstack-poisoned]
🔗 Helpful Links🧪 See artifacts and rendered test results at hud.pytorch.org/pr/pytorch/executorch/13113
Note: Links to docs will display an error until the docs builds have been completed. ❌ 2 New Failures, 1 Unrelated FailureAs of commit 0710f6c with merge base 0a2bf93 ( NEW FAILURES - The following jobs have failed:
BROKEN TRUNK - The following job 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. |
…iff adds a config to limit the maximum number of command buffers created when splitting execution between multiple command buffers. This diff introduces a new configuration option, `execute_max_cmds`, to limit the maximum number of command buffers created when splitting execution between multiple command buffers. This feature allows for more efficient management of command buffers, particularly in scenarios where the number of nodes in the graph is large. Differential Revision: [D79575908](https://our.internmc.facebook.com/intern/diff/D79575908/) ghstack-source-id: 300619367 Pull Request resolved: #13113
This pull request was exported from Phabricator. Differential Revision: D79575908 |
…ers. This diff adds a config to limit the maximum number of command buffers created when splitting execution between multiple command buffers." This diff introduces a new configuration option, `execute_max_cmds`, to limit the maximum number of command buffers created when splitting execution between multiple command buffers. This feature allows for more efficient management of command buffers, particularly in scenarios where the number of nodes in the graph is large. Differential Revision: [D79575908](https://our.internmc.facebook.com/intern/diff/D79575908/) [ghstack-poisoned]
…iff adds a config to limit the maximum number of command buffers created when splitting execution between multiple command buffers. Pull Request resolved: #13113 This diff introduces a new configuration option, `execute_max_cmds`, to limit the maximum number of command buffers created when splitting execution between multiple command buffers. This feature allows for more efficient management of command buffers, particularly in scenarios where the number of nodes in the graph is large. ghstack-source-id: 301208253 @exported-using-ghexport Differential Revision: [D79575908](https://our.internmc.facebook.com/intern/diff/D79575908/)
This pull request was exported from Phabricator. Differential Revision: D79575908 |
…ers. This diff adds a config to limit the maximum number of command buffers created when splitting execution between multiple command buffers." This diff introduces a new configuration option, `execute_max_cmds`, to limit the maximum number of command buffers created when splitting execution between multiple command buffers. This feature allows for more efficient management of command buffers, particularly in scenarios where the number of nodes in the graph is large. Differential Revision: [D79575908](https://our.internmc.facebook.com/intern/diff/D79575908/) [ghstack-poisoned]
…iff adds a config to limit the maximum number of command buffers created when splitting execution between multiple command buffers. Pull Request resolved: #13113 This diff introduces a new configuration option, `execute_max_cmds`, to limit the maximum number of command buffers created when splitting execution between multiple command buffers. This feature allows for more efficient management of command buffers, particularly in scenarios where the number of nodes in the graph is large. ghstack-source-id: 301393815 @exported-using-ghexport Differential Revision: [D79575908](https://our.internmc.facebook.com/intern/diff/D79575908/)
This pull request was exported from Phabricator. Differential Revision: D79575908 |
4439b8f
into
gh/trivedivivek/129/base
Stack from ghstack (oldest at bottom):
This diff introduces a new configuration option,
execute_max_cmds
, to limit the maximum number of command buffers created when splitting execution between multiple command buffers. This feature allows for more efficient management of command buffers, particularly in scenarios where the number of nodes in the graph is large.Differential Revision: D79575908