Closed
Investigate DuckDB TOP_N + Parquet behavior behind large-sort I/O#803
Conversation
Copilot
AI
changed the title
[WIP] Investigate large parquet sort performance
Investigate DuckDB TOP_N + Parquet behavior behind large-sort I/O
May 18, 2026
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 free
to 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.
Context
Large
ORDER BY ... LIMITqueries on 10M–20M parquet rows show multi-GB transfer and minute-scale latency despite DuckDB planningTOP_N. This PR captures root-cause evidence from DuckDB source to explain why row-group pruning is weaker than expected for this query shape.Changes
LIMIT + ORDER BYis rewritten toLOGICAL_TOP_Nand pushes a scan-side dynamic filter.PhysicalTopN.FILTER_ALWAYS_FALSE; otherwise row groups are read.SELECT *) + optional-filter handling in parquet scan/prefetch paths.SkipRowGroupvsReadRowGroupoperator logging path as the direct way to see exactly which row groups are scanned.Testing
Not applicable — no repository code changes were introduced; this PR is an investigation/evidence update.
Warning
Firewall rules blocked me from connecting to one or more addresses (expand for details)
I tried to connect to the following addresses, but was blocked by firewall rules:
production.int.allencell.org/usr/local/bin/node node /home/REDACTED/work/biofile-finder/biofile-finder/node_modules/.bin/mocha --exit(dns block)If you need me to access, download, or install something from one of these locations, you can either: