Skip to content
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

Update llama tests for block size 32 #696

Merged
merged 8 commits into from
Dec 16, 2024

Conversation

aviator19941
Copy link
Collaborator

The block_seq_stride default is changing to 32 instead of 16, so this PR updates the tests to use the block_seq_stride flag and the new numpy inputs for block size 32 to benchmark correctly. This PR also removes the decomposed fp16 tests that are not needed anymore.

@aviator19941 aviator19941 force-pushed the update_llama_test_block_sizes branch 2 times, most recently from 89d137f to 4d18c0f Compare December 16, 2024 17:32
@aviator19941 aviator19941 force-pushed the update_llama_test_block_sizes branch from 4d18c0f to f73651f Compare December 16, 2024 18:32
@aviator19941 aviator19941 merged commit ba78824 into main Dec 16, 2024
13 checks passed
@aviator19941 aviator19941 deleted the update_llama_test_block_sizes branch December 16, 2024 20:04
IanNod pushed a commit to IanNod/SHARK-Platform that referenced this pull request Dec 17, 2024
The block_seq_stride default is changing to 32 instead of 16, so this PR
updates the tests to use the block_seq_stride flag and the new numpy
inputs for block size 32 to benchmark correctly. This PR also removes
the decomposed fp16 tests that are not needed anymore.

---------

Signed-off-by: aviator19941 <[email protected]>
monorimet pushed a commit that referenced this pull request Jan 8, 2025
The block_seq_stride default is changing to 32 instead of 16, so this PR
updates the tests to use the block_seq_stride flag and the new numpy
inputs for block size 32 to benchmark correctly. This PR also removes
the decomposed fp16 tests that are not needed anymore.

---------

Signed-off-by: aviator19941 <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants