Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Print peak memory usage in EXPLAIN ANALYZE output #23874

Merged
merged 1 commit into from
Oct 23, 2024

Conversation

raunaqmorarka
Copy link
Member

@raunaqmorarka raunaqmorarka commented Oct 23, 2024

Description

E.g.

Fragment 1 [HASH]
     CPU: 384.09ms, Scheduled: 439.31ms, Blocked 2.44s (Input: 1.24s, Output: 0.00ns), Input: 1500816 rows (25.76MB); per task: avg.: 1500816.00 std.dev.: 0.00, Output: 1500000 rows (25.75MB)
     Peak memory usage: 29.70MB, Tasks count: 1; per task: max: 29.70MB
     Output layout: [orderkey, count]
     Output partitioning: SINGLE []
     Aggregate[type = FINAL, keys = [orderkey]]
     │   Layout: [orderkey:bigint, count:bigint]
     │   Estimates: {rows: 1498948 (25.73MB), cpu: 103.02M, memory: 25.73MB, network: 0B}
     │   CPU: 235.00ms (20.12%), Scheduled: 266.00ms (15.09%), Blocked: 0.00ns (0.00%), Output: 1500000 rows (25.75MB)
     │   Input avg.: 750408.00 rows, Input std.dev.: 0.03%
     │   count := count(count_0)

Additional context and related issues

Release notes

( ) This is not user-visible or is docs only, and no release notes are required.
( ) Release notes are required. Please propose a release note for me.
(x) Release notes are required, with the following suggested text:

## General
* Print peak memory usage in EXPLAIN ANALYZE output. ({issue}`23874`)

@raunaqmorarka raunaqmorarka merged commit 3acc541 into trinodb:master Oct 23, 2024
93 checks passed
@raunaqmorarka raunaqmorarka deleted the print-memory branch October 23, 2024 11:21
@github-actions github-actions bot added this to the 463 milestone Oct 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

Successfully merging this pull request may close these issues.

3 participants