-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
[Enhancement] Optimize IdChain hash code implement #47599
Conversation
Quality Gate passedIssues Measures |
[FE Incremental Coverage Report]✅ pass : 1 / 1 (100.00%) file detail
|
[BE Incremental Coverage Report]✅ pass : 0 / 0 (0%) |
@Mergifyio backport branch-3.3 |
@Mergifyio backport branch-3.2 |
@Mergifyio backport branch-3.1 |
@Mergifyio backport branch-3.0 |
@Mergifyio backport branch-2.5 |
✅ Backports have been created
|
✅ Backports have been created
|
✅ Backports have been created
|
✅ Backports have been created
|
✅ Backports have been created
|
The current implement of hashCode is easy to cause conflict. The data in the attachment takes 15 minutes to construct a HashMap<IdChain, IdChain> using the current hashCode implementation, but only takes a few seconds after changing to Arrays.hashCode(). [chain.json.tar.gz](https://github.com/user-attachments/files/16014242/chain.json.tar.gz) Signed-off-by: gengjun-git <gengjun@starrocks.com> (cherry picked from commit d6bccdb)
The current implement of hashCode is easy to cause conflict. The data in the attachment takes 15 minutes to construct a HashMap<IdChain, IdChain> using the current hashCode implementation, but only takes a few seconds after changing to Arrays.hashCode(). [chain.json.tar.gz](https://github.com/user-attachments/files/16014242/chain.json.tar.gz) Signed-off-by: gengjun-git <gengjun@starrocks.com> (cherry picked from commit d6bccdb)
The current implement of hashCode is easy to cause conflict. The data in the attachment takes 15 minutes to construct a HashMap<IdChain, IdChain> using the current hashCode implementation, but only takes a few seconds after changing to Arrays.hashCode(). [chain.json.tar.gz](https://github.com/user-attachments/files/16014242/chain.json.tar.gz) Signed-off-by: gengjun-git <gengjun@starrocks.com> (cherry picked from commit d6bccdb)
The current implement of hashCode is easy to cause conflict. The data in the attachment takes 15 minutes to construct a HashMap<IdChain, IdChain> using the current hashCode implementation, but only takes a few seconds after changing to Arrays.hashCode(). [chain.json.tar.gz](https://github.com/user-attachments/files/16014242/chain.json.tar.gz) Signed-off-by: gengjun-git <gengjun@starrocks.com> (cherry picked from commit d6bccdb)
The current implement of hashCode is easy to cause conflict. The data in the attachment takes 15 minutes to construct a HashMap<IdChain, IdChain> using the current hashCode implementation, but only takes a few seconds after changing to Arrays.hashCode(). [chain.json.tar.gz](https://github.com/user-attachments/files/16014242/chain.json.tar.gz) Signed-off-by: gengjun-git <gengjun@starrocks.com> (cherry picked from commit d6bccdb)
Why I'm doing:
The current implement of hashCode is easy to cause conflict. The data in the attachment takes 15 minutes to construct a HashMap<IdChain, IdChain> using the current hashCode implementation, but only takes a few seconds after changing to Arrays.hashCode().
chain.json.tar.gz
What I'm doing:
Fixes #https://github.com/StarRocks/StarRocksTest/issues/5336
What type of PR is this:
Does this PR entail a change in behavior?
If yes, please specify the type of change:
Checklist:
Bugfix cherry-pick branch check: