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.

Sign up for GitHub

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

Jump to bottom

Optimize retrieving Input/Variable property by index instead of property name lookup #4174

Closed
Shylock-Hg opened this issue Apr 19, 2022 · 0 comments · Fixed by #4242
Closed

Optimize retrieving Input/Variable property by index instead of property name lookup #4174

Shylock-Hg opened this issue Apr 19, 2022 · 0 comments · Fixed by #4242
Assignees
@Shylock-Hg
Labels
type/enhancement Type: make the code neat or more efficient
Milestone
v3.2.0

Comments

@Shylock-Hg
Copy link
Contributor

Shylock-Hg commented Apr 19, 2022 •
edited
Loading

Introduction

We could assume input dataset is immutable, so we could get column of input dataset by index directly.
Subjob of #4122

ps. If we flatten dataset of GetNeighbors, we could optimize Tag/Edge property by this way too.
Contents

Related work
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@Shylock-Hg Shylock-Hg

Labels
type/enhancement Type: make the code neat or more efficient
Projects
None yet
Milestone
v3.2.0
Development

Successfully merging a pull request may close this issue.

Optimize input/var property expression to get property from tuple by Shylock-Hg/nebula
1 participant
@Shylock-Hg