Skip to content
This repository was archived by the owner on Dec 13, 2023. It is now read-only.

DOC-394 | peakMemoryUsage for running and slow queries #1320

Merged
merged 3 commits into from
Apr 6, 2023
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 6 additions & 0 deletions 3.11/release-notes-api-changes311.md
Original file line number Diff line number Diff line change
Expand Up @@ -129,6 +129,12 @@ Enterprise Edition:
Like the existing `geojson` Analyzer, but with an additional `format` property
that can be set to `"latLngDouble"` (default), `"latLngInt"`, or `"s2Point"`.

#### Query API

The [`GET /_api/query/current`](http/aql-query.html#returns-the-currently-running-aql-queries)
and [`GET /_api/query/slow`](http/aql-query.html#returns-the-list-of-slow-aql-queries)
endpoints include a new numeric `peakMemoryUsage` attribute.

### Endpoints moved


Expand Down
11 changes: 11 additions & 0 deletions 3.11/release-notes-new-features311.md
Original file line number Diff line number Diff line change
Expand Up @@ -88,6 +88,17 @@ example query, but you can also specify your preferred method explicitly.

See the [`COLLECT` options](aql/operations-collect.html#method) for details.

### Extended peak memory usage reporting

The peak memory usage of AQL queries is now also reported for running queries
and slow queries.

In the web interface, you can find the **Peak memory usage** column in the
**QUERIES** section, in the **Running Queries** and **Slow Query History** tabs.

In the JavaScript and HTTP APIs, the value is reported as `peakMemoryUsage`.
See [API Changes in ArangoDB 3.11](release-notes-api-changes311.html#query-api).

## Server options

### Verify `.sst` files
Expand Down