-
Notifications
You must be signed in to change notification settings - Fork 30
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 on deeply nested topics #33
Improve performance on deeply nested topics #33
Conversation
@Harsha-Nori I think this is ready to merge now. |
Ping @slundberg |
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.
Looks good to me. Thanks!
axis=1 | ||
) | ||
return has_subtopics_df.any() | ||
|
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.
If we still have performance issues we could try vector AND operations here. But this seems good for now :)
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.
If we stick with a topic tree, I'd be more inclined to rewrite the internal datastructure to be a tree, and just use DataFrame for serialisation.
Address report of poor performance from FC people, who were using deeply nested topics.
There are two main improvements:
DataFrame.iterrows()
loops to useDataFrame.apply()
Put in basic tests of the functionality as well.