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

[Misc]: BlockHashType hash collision in v1 #11829

Closed
1 task done
WangErXiao opened this issue Jan 8, 2025 · 3 comments · Fixed by #11847
Closed
1 task done

[Misc]: BlockHashType hash collision in v1 #11829

WangErXiao opened this issue Jan 8, 2025 · 3 comments · Fixed by #11847
Labels

Comments

@WangErXiao
Copy link
Contributor

WangErXiao commented Jan 8, 2025

Anything you want to discuss about vllm.

"""Hash value of a block (int), the token IDs in the block, and extra keys.

I think this still has the potential for hash collisions. Using token IDs merely reduces the likelihood of such collisions. For example, in two sequences, if their previous block hashes are the same and the current block token IDs are also identical, a collision can still occur, albeit with a low probability.

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.
@WangErXiao WangErXiao added the misc label Jan 8, 2025
@WangErXiao
Copy link
Contributor Author

@comaniac

@comaniac
Copy link
Collaborator

comaniac commented Jan 8, 2025

Yes the probability is not zero but this should (very) rarely happen, so don't have plan on it now. You're welcome to propose RFCs and I'll be happy to review.

@WangErXiao
Copy link
Contributor Author

Yes the probability is not zero but this should (very) rarely happen, so don't have plan on it now. You're welcome to propose RFCs and I'll be happy to review.

I don’t have a very good idea at the moment. For now, we can simply add some explanations and clarifications.
#11847

@comaniac comaniac linked a pull request Jan 8, 2025 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants