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

Improve performance of _convert_arrow_to_proto #1984

Merged

Conversation

nossrannug
Copy link
Contributor

What this PR does / why we need it:

_convert_arrow_to_proto does multiple lookups in the list of column
names for the arrow table to find the index of columns. This is done for
each row so the time complexity grows quickly.
Rather than search the list of names for the index we construct a
dictionary {column_name: index}. This allows faster lookups for the
index of a column and speeds up the method significantly which affects
e.g. materialization.

NONE

@feast-ci-bot
Copy link
Collaborator

Hi @nossrannug. Thanks for your PR.

I'm waiting for a feast-dev member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

_convert_arrow_to_proto does multiple lookups in the list of column
names for the arrow table to find the index of columns. This is done for
each row so the time complexity grows quickly.
Rather than search the list of names for the index we construct a
dictionary {column_name: index}. This allows faster lookups for the
index of a column and speeds up the method significantly which affects
e.g. materialization.

Signed-off-by: Gunnar Sv Sigurbjörnsson <[email protected]>
Copy link
Member

@achals achals left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks! Do you have a sense of the perf gains for this method after this change?

@feast-ci-bot
Copy link
Collaborator

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: achals, nossrannug

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@nossrannug
Copy link
Contributor Author

Hey @achals,
I spotted this because I was materializing a feature view containing over 750 columns.
With 100 rows the total time spent in _convert_arrow_to_proto went from 15 sec down to 0.3 sec.

@achals
Copy link
Member

achals commented Oct 28, 2021

Hey @achals,

I spotted this because I was materializing a feature view containing over 750 columns.

With 100 rows the total time spent in _convert_arrow_to_proto went from 15 sec down to 0.3 sec.

That's great!!

@achals
Copy link
Member

achals commented Oct 28, 2021

/lgtm

@feast-ci-bot feast-ci-bot merged commit 66d6b78 into feast-dev:master Oct 28, 2021
@nossrannug nossrannug deleted the materialization-performance branch October 28, 2021 18:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants