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

[Usage]: Standalone Debugging and Measuring the vLLM Engine Backend #8586

Open
1 task done
htang2012 opened this issue Sep 19, 2024 · 0 comments
Open
1 task done

[Usage]: Standalone Debugging and Measuring the vLLM Engine Backend #8586

htang2012 opened this issue Sep 19, 2024 · 0 comments
Labels
usage How to use vllm

Comments

@htang2012
Copy link

htang2012 commented Sep 19, 2024

I am looking for guidance on two key aspects of working with the vLLM engine:

Debugging the vLLM Engine:

What are the recommended steps and tools for debugging the vLLM engine?
Are there any specific logs or configurations that can help in identifying performance bottlenecks or errors?

Measuring the Backend vLLM Engine Performance:

How can I measure the performance of the vLLM backend engine in isolation?
Are there any built-in metrics or tools provided by vLLM for this purpose, or would external profiling tools be more appropriate?

Right now what I am doing is through the web client application, is there anyway to do it with the vLLM Engine alone?

Thank you for your assistance!

Before submitting a new issue...

  • Make sure you already searched for relevant issues, and asked the chatbot living at the bottom right corner of the documentation page, which can answer lots of frequently asked questions.
@htang2012 htang2012 added the usage How to use vllm label Sep 19, 2024
@htang2012 htang2012 changed the title [Usage]: Debugging and Measuring the vLLM Engine Backend [Usage]: Standalone Debugging and Measuring the vLLM Engine Backend Sep 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
usage How to use vllm
Projects
None yet
Development

No branches or pull requests

1 participant