weaselab/conflict-set
2
0
Fork 0
Code Issues 4 Packages Releases 13 Activity

Range reads are slow with dense keys
All checks were successful
Tests / Release [gcc] total: 363, passed: 363
Details
GNU C Compiler (gcc) |Total|New|Outstanding|Fixed|Trend |:-:|:-:|:-:|:-:|:-: |0|0|0|0|:clap: Reference build: <a href="https://jenkins.weaselab.dev/job/weaselab/job/conflict-set/job/main/13//gcc">weaselab » conflict-set » main #13</a>
Details
Tests / Coverage total: 361, passed: 361
Details
weaselab/conflict-set/pipeline/head This commit looks good
Details

Browse Source
This commit is contained in:
Andrew Noyes
2024-02-12 15:46:56 -08:00
parent f8acc5ee86
commit d5bde56921
2 changed files with 26 additions and 22 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
ConflictSet.cpp
View File

@@ -894,9 +894,7 @@ bytes:
bool checkRangeRead(Node *n, const std::span<const uint8_t> begin,
const std::span<const uint8_t> end, int64_t readVersion,
Arena &arena) {
auto left = FirstGeqStepwise{n, begin};
while (!left.step())
;
auto left = firstGeq(n, begin);
#if DEBUG_VERBOSE && !defined(NDEBUG)
fprintf(stderr, "firstGeq for `%s' got `%s'\n", printable(begin).c_str(),