Am 01.12.2011 01:48, schrieb Michael Hunger:
Martin,
Michael, :)
would you be so kind as to test the current neo4j-1.6 snapshot with your
query?
I used neo4j 1.6 M01 community edition for my tests.
We did some changes in cypher and would like to see how that affects your
query.
Thanks a
Cypher:
START n=node:words(w_id = 137) MATCH n-[:CO_S]-m, n-[:CO_S]- t,
m-[r:CO_S]- t return m.w_id, t.w_id, r.sig, r.freq
The results are the same, but the Cypher Query is about 10 times slower
than the SQL pendant. I currently do not use any additional indices.
Just a map (words)
@Tero @Krzysztof
thx for your fast replies.
@Krzysztof
for me it was not fairly well known. I will also check out the
traverser api.
@Tero
I tried the same query using the internal id instead of my mapping index
(lucene)
orig:
START n=node:words(w_id = '137') MATCH n-[:CO_S]-m, n-[:CO_S]- t,
START n=node(119) MATCH n-[:CO_S]-m, n-[:CO_S]- t, m-[r:CO_S]- t
return m.w_id, t.w_id, r.sig, r.freq
took: 644ms (average of 100 runs after 10 warmups)
Can you try using shortestPath cypher function for m-t ?
___
Neo4j mailing list
Martin,
would you be so kind as to test the current neo4j-1.6 snapshot with your query?
We did some changes in cypher and would like to see how that affects your query.
Thanks a lot
Michael
Am 30.11.2011 um 18:34 schrieb Martin Junghanns:
@Tero @Krzysztof
thx for your fast replies.
5 matches
Mail list logo