-
Notifications
You must be signed in to change notification settings - Fork 3.8k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Browse files
Browse the repository at this point in the history
46583: workload: enhance querybench r=yuzefovich a=yuzefovich Release justification: non-production code changes. `querybench` workload has been enhanced to support queries that consist of multiple statements that are present on a single line. Previously, the workload would fail on such queries because it attempts to `Prepare` the whole line which would error out. Now we're still attempting to prepare the whole line, but if that fails, we will store plain query and will be executing it using `DB.Query` rather that `Stmt.Query`. Fixes: #46547. Fixes: #46607. Release note: None 46587: colexec: optimize resetting of buffered groups in merge joiner r=yuzefovich a=yuzefovich **colexec: fix resetting of buffered groups** Release justification: bug fixes and low-risk updates to new functionality. Previously, whenever we needed to reset the buffered groups, we would close the spilling queue and would create a new one when needed. This is an overkill since we could simply reset the spilling queues that we have which reduces amount of allocations and improves the performance. Addresses: #46502. Release note: None **logictest: make results of queries in vectorize test deterministic** Release justification: non-production code changes. Several queries in `vectorize` logic test could have produced different results, and this is now fixed. Fixes: #46630. Release note: None 46595: colexec: further optimize hash aggregator r=yuzefovich a=yuzefovich Release justification: low-risk update to new functionality (it is low-risk because it does not change anything fundamentally, rather only improves the way we handle allocations and clear an internal state). This commit optimizes the hash aggregator relationship with selection vectors. Previously, we were maintaining a map from hash code (`uint64`) to a slice of ints, and this would result in creating a new int slice for every hash code that the hash aggregator ever encounters during its run. However, we're processing atmost (about) `batchTupleLimit` tuples at once, so at most we can have the same number of different hash codes. This observation allows us to have constant number of int slices. To accommodate this, we introducing a map from hash code to the "slot" in `[][]int`, and the map is maintained to contain hash codes that we need to process. Once the hash code has been processed, the entry is deleted. This way both the map and the number of int slices stays constant throughout the run of the hash aggregator. Also this commit refactors `makeAggregateFuncs` to separate out the creation of output types (this has some impact on performance of hash aggregator which makes aggregate functions for every group). Release note: None 46668: cli,build: remove backtrace support r=yuzefovich a=petermattis Support for Backtrace Labs out of process tracers (i.e. ptrace) has been disabled since Nov 2016. We never found this integration useful. It is past time to remove it. Release justification: removal of unused code Release note: None 46673: build: do not fail RocksDB build on compiler warnings r=yuzefovich a=petermattis Disable `-Werror` for the RocksDB build which has recently started complaining about a missing exception specification in a jemalloc header with the newest version of Xcode. Release justification: low risk change to remove developer build irritation. Should be a no-op for production builds. Release note: None Co-authored-by: Yahor Yuzefovich <[email protected]> Co-authored-by: Peter Mattis <[email protected]>
- Loading branch information
Showing
18 changed files
with
202 additions
and
293 deletions.
There are no files selected for viewing
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Oops, something went wrong.
This file contains 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
This file contains 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
This file contains 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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,4 +1,4 @@ | ||
Bump the version below when changing rocksdb CMake flags. Search for "BUILD | ||
ARTIFACT CACHING" in build/common.mk for rationale. | ||
|
||
13 | ||
14 |
This file was deleted.
Oops, something went wrong.
This file was deleted.
Oops, something went wrong.
This file contains 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
This file contains 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
This file contains 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
This file contains 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
Oops, something went wrong.