Llama reimplementation with fused transaction sequence#71
Draft
Llama reimplementation with fused transaction sequence#71
Conversation
… score calculation in llama
… functions; fused-txn of more of the transformer block
…xn transpose - 3 TPS
… block fused -- 2.5 TPS
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.
Added
aiex.configureandaiex.runllama_npu.pyimplementation that makes use of that fusion. goal: all operators end-to-end run on NPU, no involvement of CPU whatsoeverstrided_copyandrepeat-- not yet very optimizedChanged
Removed
To-Do
aiex.runlowering + codegen performance improvements Xilinx/mlir-aie#2831, which this relies onxrt::elffor every token. proper solution would be to use new scratchpad memory firmware feature to read run-time parameters from DDRPR Merge Checklist
develcommit and pointing todevel.