neo4j基准测试，多个查询，测量时间

尝试在neo4j-shell内使用profile关键字。这将为您提供有关查询的速度和执行方式的一些基本事实。

这是一个简单的例子：

neo4j-sh (?)$ CREATE (a {label:"foo"})-[:bar]->(b {label: "bar"})-[:bar]->(c {label: "baz"});
+-------------------+
| No data returned. |
+-------------------+
Nodes created: 3
Relationships created: 2
Properties set: 3
1180 ms
neo4j-sh (?)$ profile match (a {label: "foo"}), (c {label: "baz"}), p=shortestPath(a-[*]-c) return p;
+--------------------------------------------------------------------------------------+
| p                                                                                    |
+--------------------------------------------------------------------------------------+
| [Node[0]{label:"foo"},:bar[0]{},Node[1]{label:"bar"},:bar[1]{},Node[2]{label:"baz"}] |
+--------------------------------------------------------------------------------------+
1 row

ColumnFilter
  |
  +ShortestPath
    |
    +Filter(0)
      |
      +AllNodes(0)
        |
        +Filter(1)
          |
          +AllNodes(1)

+--------------+------+--------+-------------+-----------------------------------------+
|     Operator | Rows | DbHits | Identifiers |                                   Other |
+--------------+------+--------+-------------+-----------------------------------------+
| ColumnFilter |    1 |      0 |             |                          keep columns p |
| ShortestPath |    1 |      0 |           p |                                         |
|    Filter(0) |    1 |      6 |             | Property(c,label(0)) == {  AUTOSTRING1} |
|  AllNodes(0) |    3 |      4 |        c, c |                                         |
|    Filter(1) |    1 |      6 |             | Property(a,label(0)) == {  AUTOSTRING0} |
|  AllNodes(1) |    3 |      4 |        a, a |                                         |
+--------------+------+--------+-------------+-----------------------------------------+

这个其他答案表明您通常正在寻找较低的DbHits值来指示更好的性能，因为这些值很昂贵。