Wrap up

Now that you’ve had the opportunity to explore the basics around Aerospike Graph and the Gremlin query language, let’s wrap things up by looking at performance metrics and shutting down the Graph environment.

Performance metrics

In Gremlin, the .profile() step is a diagnostic tool used to analyze the performance of a traversal. It provides detailed execution metrics that help understand how a query is processed by the graph engine.

Append .profile() to the end of the command to get performance metrics for a query.

g.V().has('code','DFW').profile()

Example response

Traversal Metrics
Step                                                               Count  Traversers       Time (ms)    % Dur
=============================================================================================================
FireflyGraphStep(vertex,SCAN,[code.eq(DFW)])                           1           1          15.906    82.69
FireflyScanProfileStep                                                 1           1           3.330    17.31
  FireflyScanTime                                                                              0.000
    \_ [key: code], scan count=2
    \_ 5852d53f : code = 0.000 ms
                                            >TOTAL                     -           -          19.236        -

Shut down your Graph environment

If you’re done exploring this quick start, use the following steps to exit the Gremlin Console and shut down Docker.

Exit the Gremlin Console:
Terminal window
```
:exit
```
Navigate back to the aerospike-graph root directory.
Shut down the three running Docker processes:
Terminal window
```
docker compose down
```

Congratulations on completing the Aerospike Graph quick start!

We’d love to know your thoughts on working through this guide. Share with us by using the Feedback button on the right side of this page.