Graph name, Query
Returns: String representation of a query execution plan, with details on results produced by and time spent in each operation.
GRAPH.PROFILE is a parallel entrypoint to GRAPH.QUERY. It accepts and executes the same queries, but it will not emit results,
instead returning the operation tree structure alongside the number of records produced and total runtime of each operation.
It is important to note that this blends elements of GRAPH.QUERY and GRAPH.EXPLAIN.
It is not a dry run and will perform all graph modifications expected of the query, but will not output results produced by a RETURN clause or query statistics.
Frequently Asked Questions
Does GRAPH.PROFILE modify data in the graph?
Does GRAPH.PROFILE modify data in the graph?
Yes. Unlike
GRAPH.EXPLAIN, GRAPH.PROFILE actually executes the query including any write operations (CREATE, DELETE, SET). It simply suppresses the RETURN output and instead shows execution metrics.What metrics does GRAPH.PROFILE show?
What metrics does GRAPH.PROFILE show?
For each operation in the execution plan, it shows the number of records produced and the execution time in milliseconds. This helps identify which operations are the most expensive.
What is the difference between GRAPH.EXPLAIN and GRAPH.PROFILE?
What is the difference between GRAPH.EXPLAIN and GRAPH.PROFILE?
GRAPH.EXPLAIN shows the planned execution without running the query. GRAPH.PROFILE actually runs the query and reports real execution metrics (records produced, time per operation) but does not return query results.Will GRAPH.PROFILE return results from a RETURN clause?
Will GRAPH.PROFILE return results from a RETURN clause?
No.
GRAPH.PROFILE suppresses the result set that would normally be produced by a RETURN clause. It only outputs the execution plan with runtime statistics.