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

Adding total or system peak memory usage at StatementStats #10990

Closed
miniway opened this issue Feb 9, 2022 · 4 comments
Closed

Adding total or system peak memory usage at StatementStats #10990

miniway opened this issue Feb 9, 2022 · 4 comments

Comments

@miniway
Copy link
Contributor

miniway commented Feb 9, 2022

From https://github.com/trinodb/trino/blob/master/core/trino-main/src/main/java/io/trino/server/protocol/Query.java#L745

Trino is returning only peakUserMemoryReservation to client and hiding peakNonRevocableMemoryReservation or peakTotalMemoryReservation intentionally.

But by the StatementStats there's no way to get total or system peak memory usage and might not get full sense of memory usages as memory limitations are applied to both user and system memories.

So would it be reasonable to add peakNonRevocableMemoryReservation or peakTotalMemoryReservation on the StatementStats? If so, I'll send a PR for this.

@Praveen2112
Copy link
Member

We have recently removed the distinction between system and user memory - (#10574) so we don't track - peakNonRevocableMemoryReservation but I guess we could track peakTotalMemoryReservation

cc: @findepi

@miniway
Copy link
Contributor Author

miniway commented Feb 9, 2022

It sounds great!

@findepi
Copy link
Member

findepi commented Feb 9, 2022

@miniway is there anything else TBD here?

@miniway
Copy link
Contributor Author

miniway commented Feb 10, 2022

the combined memory usage looks good. I’m closing it

@miniway miniway closed this as completed Feb 10, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

3 participants