-
-
Notifications
You must be signed in to change notification settings - Fork 350
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
unshuffleList performance #2352
Comments
This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 15 days if no further activity occurs. Thank you for your contributions. |
With the improvements in #2353 that's as much performance as we can squeeze. There are many other areas with higher priority to focus now |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 15 days if no further activity occurs. Thank you for your contributions. |
unshuffleList has never shown up in benchmarks recently. Also thanks to the eager state transition ahead of the epoch start, shaving off some milliseconds won't make a difference here |
unshuffleList() can represent a significant part of an epoch transition. This issue recaps some work to check it performance.
Changing the hash function with an echo function, estimate the total time spent hashing which is around 80%. Our hashing function could be optimized with native bindings, with a ~1.5-2x improve. With that unshuffleList() cpu time could be reduced by 40%.
The text was updated successfully, but these errors were encountered: