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

Support query cut-off #165

Closed
sherman-the-tank opened this issue Feb 26, 2019 · 1 comment
Closed

Support query cut-off #165

sherman-the-tank opened this issue Feb 26, 2019 · 1 comment
Assignees
Milestone

Comments

@sherman-the-tank
Copy link
Member

There could be power-law vertices existing in the graph. When a query hitting such vertices, the latency and the cpu cost will dramatically increase. We want to limit the impact of such query. One possible solution is to have a degree threshold. Any query will stop accessing more edges/neighbors when it reaches the threshold.

@sherman-the-tank sherman-the-tank added this to the alpha_release milestone Feb 26, 2019
@dutor dutor self-assigned this Feb 27, 2019
@jude-zhu jude-zhu modified the milestones: R201910_RC1, R201910_RC3 Nov 13, 2019
@jude-zhu jude-zhu added the later label Nov 21, 2019
@jude-zhu jude-zhu removed this from the R201910_RC3 milestone Dec 25, 2019
@jude-zhu jude-zhu added this to the v2.0.0 milestone Mar 2, 2020
@CPWstatic
Copy link
Contributor

We now have a global flag to implement this requirement, and we will implement it better by pushing down limit in the future.

yixinglu pushed a commit to yixinglu/nebula that referenced this issue Mar 21, 2022
Co-authored-by: cpw <13495049+CPWstatic@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants