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

Add truss example for Qwen1.5-110B with vllm & streaming support #282

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

Conversation

ImmarKarim
Copy link

I have created an example truss for Qwen1.5-110B LLM that was recently released. It has vllm and streaming support added.

Copy link
Contributor

@bolasim bolasim left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hey Immar! Thank you so much for the contribution. Looks great.

Just a few comments on the config and hardware requirements. Once you address those, we're looking forward to merging this PR and adding this model to our model library.

Thank you again for the contribution!

@@ -0,0 +1,19 @@
environment_variables: {CUDA_VISIBLE_DEVICES: "0,1,2,3"}
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

To use 4 devices, please up the resources below to grant you access to 4 GPUs by changing to A100:4. If you don't need 4 devices, you can drop this env var.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sure, let me change the resources section in the config file.

However, I am getting this error when dropping this env:
Screenshot 2024-05-03 at 11 08 48

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

So it turns out this error goes away with passing any random env not just CUDA_VISIBLE_DEVICES.

I just tried setting {test: "okok"} in env and model loading was a breeze.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi Immar, Can you just drop the whole environment_variables from the config? I should work better that way. I think something is off with the yaml config of this dictionary and the default should work well

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hey Bola, I have made the necessary changes. I think the workflow's awaiting approval from a maintainer.

Best

requirements:
- torch==2.1.2
- transformers==4.37.0
- vllm
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is it possible to pin the vllm version as well?

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done!

Comment on lines 15 to 16
cpu: '40'
memory: 100Gi
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please drop cpu and memory and just keep accelerator.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is also done.

Comment on lines +16 to +17
command = "ray start --head"
subprocess.check_output(command, shell=True, text=True)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't think this is still necessary with newer vlllm versions

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I was getting this error without this command. I read it somewhere online to use this if our model loading isn't being done in the main thread.

during pod startup:
Screenshot 2024-05-03 at 12 49 19

During inference:
Screenshot 2024-05-03 at 12 48 53

Copy link
Contributor

@bolasim bolasim left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for responding. Looks good in general.

@@ -0,0 +1,19 @@
environment_variables: {CUDA_VISIBLE_DEVICES: "0,1,2,3"}
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi Immar, Can you just drop the whole environment_variables from the config? I should work better that way. I think something is off with the yaml config of this dictionary and the default should work well

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