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

The performance of using java api to query nebula is weaker than that of nebula console #514

Closed
neojoe opened this issue Mar 1, 2023 · 2 comments

Comments

@neojoe
Copy link

neojoe commented Mar 1, 2023

I installed nebulagraph on the server with docker
Server configuration: cpu 16v, memory 128g, 150G ESSD cloud disk
Execute the same query logic
nebula console: MATCH p = allShortestPaths((a:point{name:"13644:5"})-[e*..7]-(b:point{name:"5119:1"})) RETURN p;
The query time is about 700ms
image

While using the nebula java api to execute the same logic, it takes 65s
image

May I ask what is the reason

@Nicole00
Copy link
Contributor

你对比下两种语言的latency, latency是服务端的执行时间
你上面提到的700ms是latency, 65s是java client的请求响应时间。 console中的请求响应时间是4m17.xxxs

@QingZ11
Copy link

QingZ11 commented May 5, 2023

@neojoe 这个 issue 超过一个月没有更新内容了,这边先行关闭了。如果你有任何更新的内容,可以再打开这个 issue 哈。

谢谢你的反馈 😊

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

3 participants