Kasper
08/30/2022, 7:41 AMnebula-bench
. Graph is deployed via docker-compose running on a 64 vCPU machine with 256GB RAM. I add a tag index to Post and rebuild:
CREATE TAG INDEX IF NOT EXISTS post_index on Post()
REBUILD TAG INDEX post_index;
After that i use lookup
.
Querying for Posts (~60M instances), this query returns in around 5 minutes:
LOOKUP ON Post yield id(vertex) | yield count(*)
whereas
LOOKUP ON Post yield id(vertex)
stalls. I tested both using console as well as python client.
Am I missing something? How should I retrieve large number of results then? Use vertex scan? Some kind of pagination?Goran Cvijanovic
08/30/2022, 7:51 AMJingchun
08/30/2022, 8:10 AMSUBMIT JOB STATS
then SHOW STATS
if you only need to get the numbers of vertices and edges.
It's better to use LIMIT and pagination when retrieving large amount of data.Kasper
08/30/2022, 8:23 AMSKIP
and LIMIT
, correct? So say if I do Match ... SKIP 1000000 LIMIT 1000000
, doesn't it still retrieve 2M results and then just discards the first 1M? Then each subsequent page would take more time.lookup
then not the right way to retrieve large numbers of results/vertex ids? From what I am aware you cannot attach a LIMIT
to a LOOKUP
query.Jingchun
08/30/2022, 8:26 AMLOOKUP ON Post yield id(vertex) | LIMIT 10, 10
Kasper
08/30/2022, 8:30 AMJingchun
08/30/2022, 8:38 AMKasper
08/30/2022, 9:25 AMJingchun
08/30/2022, 9:26 AMKasper
08/30/2022, 9:28 AMJingchun
08/30/2022, 9:28 AMGoran Cvijanovic
08/30/2022, 10:53 AMwey
08/31/2022, 12:19 AM