-
Notifications
You must be signed in to change notification settings - Fork 413
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
Qualcomm AI Engine Direct - Optimize static llama phase 2 #7466
base: main
Are you sure you want to change the base?
Qualcomm AI Engine Direct - Optimize static llama phase 2 #7466
Conversation
shewu-quic
commented
Jan 2, 2025
•
edited
Loading
edited
- Modify custom annotation for kv in llama
- Remove unneccesary reshape op
- Refactor requantize mechanism
- Support partial of ops to insert to_copy
- For the same quant_attr share the same to_copy op
- Remove qdq for I/O
- Refine calibration and runner in prefill mode
- (new) Support graph sharding in hybrid mode
🔗 Helpful Links🧪 See artifacts and rendered test results at hud.pytorch.org/pr/pytorch/executorch/7466
Note: Links to docs will display an error until the docs builds have been completed. ❌ 1 New FailureAs of commit 9def8ff with merge base 7a2dc47 (): NEW FAILURE - The following job has failed:
This comment was automatically generated by Dr. CI and updates every 15 minutes. |
This PR needs a
|
@cccclai has imported this pull request. If you are a Meta employee, you can view this diff on Phabricator. |
Hey can you help rebase? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM and thank you for the refactor!
- Modify custom annotation for kv in llama - Remove unneccesary reshape op - Refactor requantize mechanism - Support partial of ops to insert to_copy - For the same quant_attr share the same to_copy op - Remove qdq for I/O - Refine calibration and runner in prefill mode - Support graph sharding in hybrid mode
b914a15
to
9def8ff
Compare
I have rebased. I add graph sharding support in hybrid mode. This has the most significant impact on performance. When HTP execution time exceeds RPC polling time (10 ms in burst mode), CPU frequency may drop to its minimum. Our experiments indicate that setting num_sharding to 4 yields the best results. However, this depends on the device. Aim to keep the execution time for each partition under 10ms ( RPC polling time).
|
@cccclai has imported this pull request. If you are a Meta employee, you can view this diff on Phabricator. |