[V1] Feedback Thread

[simon-mo]

Please leave comments here about your usage of V1, does it work? does it not work? which feature do you need in order to adopt it? any bugs?

For bug report, please file it separately and link the issue here.

For in depth discussion, please feel free to join #sig-v1 in the vLLM Slack workspace.

[robertgshaw2-redhat]

• [Bug]: V1 Regression: ValueError: could not broadcast input array from shape (y,) into shape (x,) #12567

[wedobetter]

👍 I have not done a proper benchmark but V1 feels superior, i.e. higher throughput + lower latency, TTFT.
The other thing that I have noticed is that logging has changed Running: 1 reqs, Waiting: 0 reqs, it used to print stats such token/s.

I have encountered a possible higher memory consumption issue, but am overall very pleased with the vllm community's hard work on V1.
#12529

[m-harmonic]

Does anyone know about this bug with n>1? Thanks
#12584

[robertgshaw2-redhat]

Does anyone know about this bug with n>1? Thanks #12584

Thanks, we are aware and have some ongoing PRs for it.

#10980

[robertgshaw2-redhat]

I have encountered a possible higher memory consumption issue, but am overall very pleased with the vllm community's hard work on V1.

Logging is in progress. Current main has a lot more and we will maintain compatibility with V0. Thanks!

[dchichkov]

Quick feedback [VLLM_USE_V1=1]:

• n > 1 would be nice

• guided_grammar (or anything guided really) would be nice

[robertgshaw2-redhat]

Quick feedback [VLLM_USE_V1=1]:

• n > 1 would be nice
• guided_grammar (or anything guided really) would be nice

Thanks, both are in progress

[hibukipanim]

are logprobs output (and specifically prompt logprobs with echo=True) expected to be working with current V1 (0.7.0)?
checking here before opening an issue to reproduce

[akshay-loci]

Maybe there is a better place to discuss this but the implementation for models that use more than one extra modality is quite non-intuitive. get_multimodal_embeddings() expects that we return a list or tensor of length equal to the number of multimodal items provided in the batch and we then have to make unintuitive assumptions on how the output passed into get_input_embeddings would look like because the batching being used while calling both functions is not the same. It would be much nicer if for example the input and output of get_multimodal_embeddings are dicts with the keys being the different modalities.

[robertgshaw2-redhat]

are logprobs output (and specifically prompt logprobs with echo=True) expected to be working with current V1 (0.7.0)? checking here before opening an issue to reproduce

Still in progress

[wedobetter]

👍 I have not done a proper benchmark but V1 feels superior, i.e. higher throughput + lower latency, TTFT. The other thing that I have noticed is that logging has changed Running: 1 reqs, Waiting: 0 reqs, it used to print stats such token/s.

I have encountered a possible higher memory consumption issue, but am overall very pleased with the vllm community's hard work on V1. #12529

Thanks for fixing metrics logs in 0.7.1!
Lack of pipeline parallelism in V1 is a show stopper for production deployments #11945