When modelling the airports in our airline network and routes between them, with localized properties on each of them, I found it easiest to have a Destination node that had all of the relationships with other Destinations, etc and then have one Dest...
Reducing cardinality in the query is a delicate balancing act, but a critical exercise in making queries like yours return in a reasonable time. There are many presentations on Cypher Query Optimization.
Since you are really only interested in the pr...
Indexes are only used to find the starting nodes in a match, like the (n) in your query.
The problem is likely in your undirected, variable-length relationship. Are your relationships really directionless? Without a label on the relationship, it is c...
You have to start from an empty database (in Community), so it all all or nothing proposition.
The tipping point used to be 100,000 or 1 million(ish) rows. I can't remember which. It was a big effort to code up the file generation, but the speed of l...
At that scale, if you are starting from an empty database, you should really look at Neo4j Import.
You have to do a lot of the pre-processing yourself in your Python script, but the import speed will remarkably fast. You would write out one (or more)...
