-
Notifications
You must be signed in to change notification settings - Fork 123
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
Improve performance of ShortNameComparator. #1027
Improve performance of ShortNameComparator. #1027
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we think the performance improvements will be primarily speed, memory utilization, or both?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is there a trick to recreate the profile you describe in #135 ? I've been trying to use the profiler on our main branch to observe the described behavior and I'm not having any luck. I guess there have to be a lot of children extracted - I tried dumping in all kinds of archive input to see if I can see something similar on the profiler, but I'm not observing what you were.
Yes, this optimization is designed for objects with a large number of children (i.e. 100,000 or more). Let me know if you would like me to generate an object for you. |
Nah, I believe you. It's not that big of a change really. |
Based on the profiling results in the original PR, this change should improve both speed and memory usage as in the normal case of sorting numerical children it creates virtually no objects. |
I meant the algorithm is basically the same, but yes, I can see how it's a less heavy handed implementation. |
This is an updated version of #135 .