I'm sure someone will come along and say something more useful, but yes,
how you have understood it is correct. If an Index is used the
TraversalMatcher row will be replaced with SchemaIndex row and dbhits
should go right down.
M
On Thursday, 16 October 2014 11:04:06 UTC+1, Alex winter wrote:
>
> Could sb explain for me the meaning of dbhits when we put "profile" prefix
> in cypher query?
>
> for example:
>
>
> +------------------+------+--------+-------------+-----------------------------+
> | Operator | Rows | DbHits | Identifiers |
> Other |
>
> +------------------+------+--------+-------------+-----------------------------+
> | ColumnFilter | 10 | 0 | | keep columns
> person |
> | Slice | 10 | 0 | | {
> AUTOINT1} |
> | TraversalMatcher | 10 | 13 | | person, UNNAMED14,
> person |
>
> As I understand that dbhits mean the number neo4j access database? Is it
> right? So the cypher query performance depends on the number of dbhits or
> not (of course it also depend how e cache data) but if the number of dbhits
> is small, the performance is better?
>
> Thanks in advance
>
--
You received this message because you are subscribed to the Google Groups
"Neo4j" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
