Skip to content

Conversation

tdoublep
Copy link
Member

@tdoublep tdoublep commented Sep 9, 2025

Purpose

An initial implementation of span semantics in vLLM.

Please note that this has a known bug dealing with concurrent sequences that re-use the same span in different locations. We are working on a solution for this, but in the meantime accuracy may be negatively affected.

Test Plan

n/a

Test Result

n/a


Essential Elements of an Effective PR Description Checklist
  • The purpose of the PR, such as "Fix some issue (link existing issues this PR will resolve)".
  • The test plan, such as providing test command.
  • The test results, such as pasting the results comparison before and after, or e2e results
  • (Optional) The necessary documentation update, such as updating supported_models.md and examples for a new model.
  • (Optional) Release notes update. If your change is user facing, please update the release notes draft in the Google Doc.

Co-authored-by: Nathan Ordonez <[email protected]>
Signed-off-by: Thomas Parnell <[email protected]>
@tdoublep tdoublep merged commit fb48545 into main Sep 19, 2025
1 check passed
@tdoublep tdoublep deleted the spans-tpa branch September 19, 2025 05:18
nataxcan added a commit that referenced this pull request Sep 24, 2025
An initial implementation of span semantics in vLLM.

Please note that this has a known bug dealing with concurrent sequences
that re-use the same span in different locations. We are working on a
solution for this, but in the meantime accuracy may be negatively
affected.

n/a

n/a

---
<details>
<summary> Essential Elements of an Effective PR Description Checklist
</summary>

- [x] The purpose of the PR, such as "Fix some issue (link existing
issues this PR will resolve)".
- [ ] The test plan, such as providing test command.
- [ ] The test results, such as pasting the results comparison before
and after, or e2e results
- [ ] (Optional) The necessary documentation update, such as updating
`supported_models.md` and `examples` for a new model.
- [ ] (Optional) Release notes update. If your change is user facing,
please update the release notes draft in the [Google
Doc](https://docs.google.com/document/d/1YyVqrgX4gHTtrstbq8oWUImOyPCKSGnJ7xtTpmXzlRs/edit?tab=t.0).
</details>

---------

Signed-off-by: Thomas Parnell <[email protected]>
Signed-off-by: Nathan Ordonez <[email protected]>
Co-authored-by: Nathan Ordonez <[email protected]>
Co-authored-by: Nathan Ordonez <[email protected]>
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