Hi Mattias, thanks for the update. We are really struggling with this one,
because we are at a performance with Neo4j at about 4 sec and a comparable
query in a MariaDB SQL instance of 0.17 sec.
On Wednesday, 19 March 2014 14:32:28 UTC+1, Mattias Persson wrote:
>
> This issue has been fixed and
This issue has been fixed and will be included in the next milestone.
2014-03-08 19:29 GMT+01:00 Tom Zeppenfeldt :
> And yes.. it happens with other queries as well ..
>
> and query times are a lot longer then expected with a db of this size,
> although I indexed the crucial parts.
>
> neo4j-sh (
And yes.. it happens with other queries as well ..
and query times are a lot longer then expected with a db of this size,
although I indexed the crucial parts.
neo4j-sh (?)$ schema
Indexes
ON :Person(id)ONLINE (for uniqueness constraint)
ON :Term(id) ONLINE
Hi Tom,
does this happen with any database? I.e. imported by your load-csv script?
I asked my colleagues to look into it. Perhaps related to some changes in the
relationship-store in Neo4j 2.1
Do you see similar behavior also for other queries?
Cheers,
Michael
(michael}-[:SUPPORTS]->(YO
I have a graph db with about 1 docs (:jurt) and about 12000 terms
(t:Term) from a vocabulary. There are about 1.2M relationships of type
(j:jurt)-[:HAS_TERM]->(t:Term)
To find out which documents are similar to a given document, based on a
count of common terms, I use this query
match (
