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

Querying NebulaGraph using the Nebula Python API is significantly slower than using the Nebula Console. #266

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

Comments

@neojoe
Copy link

neojoe commented Mar 1, 2023

我在服务器上用docker的方式安装nebulagraph
服务器配置:cpu 16v ,内存128g,150G ESSD云盘
执行相同的查询逻辑
nebula onsole:MATCH p = allShortestPaths((a:point{name:"13644:5"})-[e*..7]-(b:point{name:"5119:1"})) RETURN p;
查询时间是700ms左右
image
而用nebula python api 执行相同的逻辑,花费65s
image
请问是什么原因?

@neojoe
Copy link
Author

neojoe commented Mar 1, 2023

java api 也是同样的问题

@neojoe neojoe changed the title 通过nebula python API 查询nubulagraph 比nebula console 通过nebula python API 查询nubulagraph 比nebula console 性能慢很多 Mar 1, 2023
@wey-gu
Copy link
Contributor

wey-gu commented Mar 2, 2023

Ping @Aiee @Nicole00 is this related to serialization time, or?

@Nicole00
Copy link
Contributor

Nicole00 commented Sep 5, 2023

你可以看下console中执行结果会有两个时间,700ms 是执行结果ResultSet中的latency时间,后面那个是客户端执行的总体时间。

如果要对比其他客户端,可以通过同时对比resultSet.getLatency 或者 同时对比 客户端执行总时间 来确定各个客户端的性能差异。

@QingZ11 QingZ11 changed the title 通过nebula python API 查询nubulagraph 比nebula console 性能慢很多 Querying NebulaGraph using the Nebula Python API is significantly slower than using the Nebula Console. Sep 18, 2023
@QingZ11
Copy link

QingZ11 commented Sep 18, 2023

@neojoe hi, if your problem is solved, would you like to close the issue? Thanks a lot for your contribution.

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