Uh oh!
There was an error while loading. Please reload this page.
PHOENIX-6436 OrderedResultIterator overestimates memory requirements. - #1189
Merged
Conversation
ContributorAuthor
It turns out that for large sets Trino is actually performing the topN faster, even though it has to pull in all the data. This is due to the final client merge work that Phoenix is doing. |
stoty
commented
Apr 5, 2021
Contributor
💔 -1 overall
This message was automatically generated. |
lhofhansl
commented
Apr 5, 2021
ContributorAuthor
Thanks @gjacoby126 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
See Jira.
the OrderedResultIterator will store topN values in either a BufferedQueue or a SizeBoundQueue. Each limit the memory used to the passed thresholdBytes (default is 20MB), the BufferQueue will spool to disk when reaching that size, SizeBoundQueue will fail.
Hence we additionally limit the worst case memory consumption to thresholdBytes.
I noticed this when implementing limit and topN pushdown for the Trino Phoenix connector: trinodb/trino#7490