-
-
Notifications
You must be signed in to change notification settings - Fork 9.3k
[MODEL] add Exaone model support #7819
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
👋 Hi! Thank you for contributing to the vLLM project. Once the PR is approved and ready to go, please make sure to run full CI as it is required to merge (or just use auto-merge). To run full CI, you can do one of these:
🚀 |
c857d59
to
449aa30
Compare
Checked the ruff format and fixed the code. |
Solve #7236 Summary of changes
Test Result
|
Here is benchmark result with A100 40GB * 2. (tensor-parallel-size 2)
Throuhput benchmark result (Click to Expand)
Throughput: 13.87 requests/s, 6343.01 tokens/s |
Here is benchmark result with A100 40GB * 1. (--quantization fp8)
Throuhput benchmark result
Throughput: 12.60 requests/s, 5765.20 tokens/s |
/ready |
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.
I'm not sure what to "choose" between this and the other PR #7942, but this one does have the README update and also gets a good accuracy score, so I am accepting this one.
lm_eval --model vllm --model_args pretrained=LGAI-EXAONE/EXAONE-3.0-7.8B-Instruct,max_model_len=4096,enable_chunked_prefill=True --tasks gsm8k --batch_size auto
vllm (pretrained=LGAI-EXAONE/EXAONE-3.0-7.8B-Instruct,max_model_len=4096,enable_chunked_prefill=True), gen_kwargs: (None), limit: None, num_fewshot: None, batch_size: auto
|Tasks|Version| Filter |n-shot| Metric | |Value | |Stderr|
|-----|------:|----------------|-----:|-----------|---|-----:|---|-----:|
|gsm8k| 3|flexible-extract| 5|exact_match|↑ |0.8044|± |0.0109|
| | |strict-match | 5|exact_match|↑ |0.8021|± |0.0110|
Sorry before we merge, a common question we ask is how is this different from llama implementation, and why can't the existing llama implementation run it. For example, we have Mistral, InternLMForCausalLM, and AquilaForCausalLM all mapped directly to llama.py |
Thank you for accepting this PR! I'll add to @Deepfocused's partial answer to your question and explain the whole change. (#7942 (comment)) The Exaone3 model is Llama based code, but when it pre-trained the model from scratch, it changed the tokenizer and changed some model configs such as keys and values. The changes are as follows:
These two differences make it unlikely that a directly mapping to llama.py would be applicable. If there is another way to map it, please leave a reference PR. I'll update the code. (While off-topic, It's nice to have a convenient way to evaluate performance using lm_eval. If I do a new model PR in the future, I will include performance evaluation results. Thanks for letting me know!) |
Update: It's just the modeling file inside vLLM that's broken. I'll open a PR to fix it. |
Signed-off-by: Alvant <[email protected]>
Signed-off-by: LeiWang1999 <[email protected]>
Recently, The new model exaone released. I would love to contribute the new model to vLLM as well.
In this PR, I have provided the implementation of EXAONE-3.0 model and add model configs.
BEFORE SUBMITTING, PLEASE READ THE CHECKLIST BELOW AND FILL IN THE DESCRIPTION ABOVE
PR Checklist (Click to Expand)
Thank you for your contribution to vLLM! Before submitting the pull request, please ensure the PR meets the following criteria. This helps vLLM 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.[Frontend]
For changes on the vLLM frontend (e.g., OpenAI API server,LLM
class, etc.)[Kernel]
for changes affecting CUDA kernels or other compute kernels.[Core]
for changes in the core vLLM logic (e.g.,LLMEngine
,AsyncLLMEngine
,Scheduler
, etc.)[Hardware][Vendor]
for hardware-specific changes. Vendor name should appear in the prefix (e.g.,[Hardware][AMD]
).[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:
format.sh
to format your code.docs/source/
if the PR modifies the user-facing behaviors of vLLM. It helps vLLM 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 excluding kernel/data/config/test), 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.What to Expect for the Reviews
The goal of the vLLM team is to be a transparent reviewing machine. We would like to make the review process transparent and efficient and make sure no contributor feel confused or frustrated. However, the vLLM team is small, so we need to prioritize some PRs over others. Here is what you can expect from the review process:
action-required
label on the PR if there are changes required. The contributor should address the comments and ping the reviewer to re-review the PR.Thank You
Finally, thank you for taking the time to read these guidelines and for your interest in contributing to vLLM. Your contributions make vLLM a great tool for everyone!