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

Port llama3 support from vLLM #45

Open
wants to merge 3 commits into
base: main
Choose a base branch
from

Conversation

kasohrab
Copy link
Contributor

@kasohrab kasohrab commented Nov 13, 2024

Ports llama3 support from vLLM. I used the offline inference script to test llama2, llama3,3.1,3.2 (only text variants, not multi-modal) and other models too for backwards compatibility.

BEFORE SUBMITTING, PLEASE READ THE CHECKLIST BELOW AND FILL IN THE DESCRIPTION ABOVE


PR Checklist (Click to Expand)

Thank you for your contribution to Vidur! Before submitting the pull request, please ensure the PR meets the following criteria. This helps Vidur maintain the code quality and improve the efficiency of the review process.

PR Title and Classification

Only specific types of PRs will be reviewed. The PR title is prefixed appropriately to indicate the type of change. Please use one of the following:

  • [Bugfix] for bug fixes.
  • [CI/Build] for build or continuous integration improvements.
  • [Doc] for documentation fixes and improvements.
  • [Model] for adding a new model or improving an existing model. Model name should appear in the title.
  • [Profiling] For changes on the profiling module.
  • [Core] for changes in the core simulator logic
  • [Misc] for PRs that do not fit the above categories. Please use this sparingly.

Note: If the PR spans more than one category, please include all relevant prefixes.

Code Quality

The PR need to meet the following code quality standards:

  • Pass all linter checks. Please use make format to format your code.
  • The code need to be well-documented to ensure future contributors can easily understand the code.
  • Please add documentation to docs/source/ if the PR modifies the user-facing behaviors of Vidur. It helps user understand and utilize the new features or changes.

Notes for Large Changes

Please keep the changes as concise as possible. For major architectural changes (>500 LOC), we would expect a GitHub issue (RFC) discussing the technical design and justification. Otherwise, we will tag it with rfc-required and might not go through the PR.

Thank You

Finally, thank you for taking the time to read these guidelines and for your interest in contributing to Vidur. Your contributions make Vidur a great tool for everyone!

@AgrawalAmey
Copy link
Contributor

@kasohrab which all models did you test?

@kasohrab
Copy link
Contributor Author

@kasohrab which all models did you test?

I tested at least one model variant from each family in the description (llama2, llama3,3.1,3.2) plus one mixtral model so far.

@AgrawalAmey
Copy link
Contributor

AgrawalAmey commented Nov 14, 2024

I meant like in llama 3.2, does 10b, 90b etc work with these set of changes?

@kasohrab
Copy link
Contributor Author

I meant like in llama 3.2, does 10b, 90b etc work with these set of changes?

in llama 3.2, just 1B and 3B work with this pr. I believe 10b and 90b would require further work porting mllama arch: https://github.com/vllm-project/vllm/blob/main/vllm/model_executor/models/mllama.py.

@kasohrab
Copy link
Contributor Author

let me know if that should be part of this pr @AgrawalAmey

@AgrawalAmey
Copy link
Contributor

@kasohrab it would be fantastic if we could port just the language model part to support 10 and 90b models. it would also be good since it would allow us to run 1-10B pair. but we can also take this up later if you expect this to take a lot of effort.

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