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

Remove distinction between system and user memory #10574

Merged
merged 1 commit into from
Jan 24, 2022

Conversation

findepi
Copy link
Member

@findepi findepi commented Jan 12, 2022

No description provided.

@findepi
Copy link
Member Author

findepi commented Jan 12, 2022

cc @erichwang

@sopel39 sopel39 requested a review from martint January 12, 2022 14:03
@losipiuk
Copy link
Member

❤️

@findepi findepi force-pushed the findepi/split-hair-on-memory branch from ca02083 to cda4433 Compare January 13, 2022 13:21
@cla-bot cla-bot bot added the cla-signed label Jan 13, 2022
@findepi findepi force-pushed the findepi/split-hair-on-memory branch from cda4433 to e67a592 Compare January 13, 2022 14:06
@findepi findepi force-pushed the findepi/split-hair-on-memory branch 3 times, most recently from b6f514c to 40046c0 Compare January 14, 2022 11:53
@losipiuk
Copy link
Member

// enforced against user memory allocations
private DataSize maxQueryMemory = DataSize.of(20, GIGABYTE);
// enforced against user + system memory allocations (default is maxQueryMemory * 2)
private DataSize maxQueryTotalMemory;

remainder?

@losipiuk
Copy link
Member

@losipiuk
Copy link
Member

QueryStats still has user/total distincition. On purpose?

@findepi
Copy link
Member Author

findepi commented Jan 14, 2022

// enforced against user memory allocations
private DataSize maxQueryMemory = DataSize.of(20, GIGABYTE);
// enforced against user + system memory allocations (default is maxQueryMemory * 2)
private DataSize maxQueryTotalMemory;

remainder?

No. The from cluster memory manager perspective, total memory = user + revocable.
I've updated the docs to make it clear.

QueryStats still has user/total distincition. On purpose?

same

@@ -156,15 +153,13 @@ public SqlTaskManager(

this.localMemoryManager = requireNonNull(localMemoryManager, "localMemoryManager is null");
DataSize maxQueryMemoryPerNode = nodeMemoryConfig.getMaxQueryMemoryPerNode();
DataSize maxQueryTotalMemoryPerNode = nodeMemoryConfig.getMaxQueryTotalMemoryPerNode();
queryMaxMemoryPerTask = nodeMemoryConfig.getMaxQueryTotalMemoryPerTask();
queryMaxMemoryPerTask = nodeMemoryConfig.getMaxQueryMemoryPerTask();
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

preexistent - can you still rename this to maxQueryMaxMemoryPerTask

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

you mean to swap "query" and "max"? let's follow up

@findepi findepi force-pushed the findepi/split-hair-on-memory branch from af8fe86 to cf6370a Compare January 14, 2022 13:16
@findepi
Copy link
Member Author

findepi commented Jan 14, 2022

(squashed)

@findepi
Copy link
Member Author

findepi commented Jan 15, 2022

CI #10631, was green before squash.
rerunning.

@findepi findepi force-pushed the findepi/split-hair-on-memory branch from 1ab032c to aae7ab8 Compare January 21, 2022 17:34
@findepi
Copy link
Member Author

findepi commented Jan 21, 2022

(rebased)

@findepi findepi force-pushed the findepi/split-hair-on-memory branch 2 times, most recently from e0a4a82 to b3b9b8d Compare January 21, 2022 20:19
@ElapsedSoul
Copy link

Old configurations are:

max-total-memory-per-node=40GB
max-memory-per-node=32GB

which value should max-memory-per-node now be?
32 or 40?

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.

4 participants