impala-reviews mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tim Armstrong (Code Review)" <>
Subject [Impala-ASF-CR] IMPALA-5677: limit clean page memory consumption
Date Wed, 16 Aug 2017 21:49:03 GMT
Tim Armstrong has posted comments on this change.

Change subject: IMPALA-5677: limit clean page memory consumption

Patch Set 1:

Commit Message:

Line 34: Ran in a loop to flush out any flakiness.
> do we explicitly test the clean_page_limit={0, buffer_pool_limit} cases?
I don't have tests for those. We could add a backend test for those cases. There isn't a distinct
code path for those cases but I guess it's good to test the edge cases.
File be/src/common/

PS1, Line 61: spilled
> maybe say "unpinned", since "spilled" is more of a operator concept rather 
File be/src/runtime/bufferpool/

Line 109:   int64_t GetCleanPageBytes();
> is that still used?

PS1, Line 636: one page
> what does that mean? maybe say, "no other page to evict"?
File be/src/runtime/bufferpool/buffer-allocator.h:

PS1, Line 222: the
> they?

PS1, Line 225: remaining
> I'm not sure it's clear what it means to be "remaining".
Reworded the comment.

PS1, Line 228: clean_page_bytes_remaining_
> also, this name might be a little confusing. It's nice that it's consistent
Documented that this is clean_page_bytes_limit_ - bytes of clean pages. I think that makes
it less ambiguous.

To view, visit
To unsubscribe, visit

Gerrit-MessageType: comment
Gerrit-Change-Id: Ib6b687ab4bdddf07d9d6c997ff814aa3976042f9
Gerrit-PatchSet: 1
Gerrit-Project: Impala-ASF
Gerrit-Branch: master
Gerrit-Owner: Tim Armstrong <>
Gerrit-Reviewer: Dan Hecht <>
Gerrit-Reviewer: Tim Armstrong <>
Gerrit-HasComments: Yes

View raw message