AQL Execution and Performance

All queries that have successfully run to completion return statistics about the execution

Clients can check if given AQL queries are syntactically valid using an HTTP API or JavaScript API

You can explain and profile AQL queries to inspect the execution plans and to understand the performance characteristics, as well as create debug packages for reporting issues

For understanding the performance of specific queries, you can profile them to identify slow parts of query execution plans

AQL queries are sent through an optimizer before execution that creates an initial execution plan, looks for optimization opportunities, and applies them

AQL provides an optional query results cache in single server deployments

You can optionally let ArangoDB write metadata of finished AQL queries to a collection for later analysis