Query optimalisation

(Michael Hunger) #22

I just ran this with your data on my laptop (with 4G PC and 2G heap configured).

PROFILE
CALL db.index.fulltext.queryNodes("messages", "someren brand") yield node as message
WHERE 1546281754000 <= message.sended <= 1548960154000
RETURN message.uuid

It finished in less than 200ms

0 Likes

(Tomswinkels) #23

Hmmm thats sounds good.

But then i run that query:

Started streaming 2310 records after 39 ms and completed after 22869 ms, displaying first 1000 rows.

0 Likes

(Michael Hunger) #24

What is your memory (heap + page-cache config again)?
What kind of disk are you running?

0 Likes

(Tomswinkels) #25

This are the settings that i use now:

dbms.memory.heap.initial_size=3000m
dbms.memory.heap.max_size=3000m
dbms.memory.pagecache.size=1000m

150GB SSD disk.

0 Likes

(Tomswinkels) #26

I have change the settings to:

dbms.memory.heap.initial_size=2000m
dbms.memory.heap.max_size=2000m
dbms.memory.pagecache.size=4000m

Cypher version: CYPHER 3.5, planner: COST, runtime: SLOTTED. 121489 total db hits in 17191 ms.

Maybe you result is from the second (cache) run?

0 Likes

(Michael Hunger) #27

Yes very likely as i ran multiple queries there. The page-cache should be warmed up.

I just ran it on my laptop and it was fast enough.

0 Likes