-
Notifications
You must be signed in to change notification settings - Fork 645
Faster weight only quantized gemm #12862
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
Conversation
🔗 Helpful Links🧪 See artifacts and rendered test results at hud.pytorch.org/pr/pytorch/executorch/12862
Note: Links to docs will display an error until the docs builds have been completed. ✅ No FailuresAs of commit 581503e with merge base d5232a0 ( This comment was automatically generated by Dr. CI and updates every 15 minutes. |
This pull request was exported from Phabricator. Differential Revision: D78994081 |
This PR needs a
|
Summary: ## Context As title. Provide an implementation for the `gemm` counterpart of the weight int4 quantized `gemv` implementation added in D78275584 / pytorch#12444. This new kernel is quite similar to the existing one, with the primary difference being that it uses the same weight packing used in the `gemv` implementation. ## Next Steps * Reduce framework overhead from command buffer re-encoding between tokens. Achieve this by caching more artifacts that can be re-used between command buffer encodings, and only re-encoding command buffers when necessary. * Experiment with dynamic quantization, which should provide speedup via int8 dot product extension Reviewed By: digantdesai Differential Revision: D78994081
Summary: Pull Request resolved: pytorch#12862 ## Context As title. Provide an implementation for the `gemm` counterpart of the weight int4 quantized `gemv` implementation added in D78275584 / pytorch#12444. This new kernel is quite similar to the existing one, with the primary difference being that it uses the same weight packing used in the `gemv` implementation. ## Next Steps * Reduce framework overhead from command buffer re-encoding between tokens. Achieve this by caching more artifacts that can be re-used between command buffer encodings, and only re-encoding command buffers when necessary. * Experiment with dynamic quantization, which should provide speedup via int8 dot product extension Reviewed By: digantdesai Differential Revision: D78994081
This pull request was exported from Phabricator. Differential Revision: D78994081 |
Summary: ## Context As title. Provide an implementation for the `gemm` counterpart of the weight int4 quantized `gemv` implementation added in D78275584 / pytorch#12444. This new kernel is quite similar to the existing one, with the primary difference being that it uses the same weight packing used in the `gemv` implementation. ## Next Steps * Reduce framework overhead from command buffer re-encoding between tokens. Achieve this by caching more artifacts that can be re-used between command buffer encodings, and only re-encoding command buffers when necessary. * Experiment with dynamic quantization, which should provide speedup via int8 dot product extension Reviewed By: digantdesai Differential Revision: D78994081
This pull request was exported from Phabricator. Differential Revision: D78994081 |
Summary:
Context
As title. Provide an implementation for the
gemm
counterpart of the weight int4 quantizedgemv
implementation added in D78275584 / #12444.This new kernel is quite similar to the existing one, with the primary difference being that it uses the same weight packing used in the
gemv
implementation.Next Steps
Reduce framework overhead from command buffer re-encoding between tokens. Achieve this by caching more artifacts that can be re-used between command buffer encodings, and only re-encoding command buffers when necessary.
Experiment with dynamic quantization, which should provide speedup via int8 dot product extension
Differential Revision: D78994081