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

limit performance #3228

Open
he7g opened this issue Oct 28, 2021 · 1 comment
Open

limit performance #3228

he7g opened this issue Oct 28, 2021 · 1 comment
Labels
community Source: who proposed the issue type/enhancement Type: make the code neat or more efficient

Comments

@he7g
Copy link

he7g commented Oct 28, 2021

nebula version: 2.6.0

image

The returned number rows is 1, but offset is not same. Offset more bigger, more costs?

And match (v)-[r:VICE_MAIN]->(v2) return r limit 1; VS match (v)-[r:VICE_MAIN]->(v2) return r limit 100000; costs same.

2.6.0 didn't optimize for this???
@he7g he7g added the type/bug Type: something is unexpected label Oct 28, 2021
@Shylock-Hg
Copy link
Contributor

2.6.0 don't optimize the offset.

@jamieliu1023 jamieliu1023 mentioned this issue Nov 1, 2021
Closed
@Sophie-Xie Sophie-Xie added type/enhancement Type: make the code neat or more efficient and removed type/bug Type: something is unexpected labels Nov 4, 2021
@Sophie-Xie Sophie-Xie added the community Source: who proposed the issue label Nov 24, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
community Source: who proposed the issue type/enhancement Type: make the code neat or more efficient
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@he7g @Shylock-Hg @Sophie-Xie