Repository navigation
Record only the first result timestamp in WatDiv, and bump jbr to 6.6.0 - #22
Merged
rubensworks merged 1 commit intoNov 15, 2026
Merged
Conversation
At scale 1000, recording the time of every result made query-times.csv and query-results-raw.json about 1 GB each per combination, almost all from C3. jbr 6.6.0 adds queryRunnerRecordTimestamps, set to "first" for WatDiv, which keeps the time to the first result for psbr's plots. jbr 6.6.0 also creates generated/ before preparing, so Docker no longer creates it owned by root, and -f regenerates a shared generated/ only once. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01UNM2PDyzVijfquXVY2Av52
rubensworks
deleted the
claude/lucid-meitner-jg4dy5-record-timestamps
branch
November 15, 2026 05:03
rubensworks
restored the
claude/lucid-meitner-jg4dy5-record-timestamps
branch
November 15, 2026 05:03
rubensworks
deleted the
claude/lucid-meitner-jg4dy5-record-timestamps
branch
November 15, 2026 05:05
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.
At WatDiv scale 1000, each combination's
query-times.csvandquery-results-raw.jsonwere about 1 GB each, almost all of it the time of every result of C3 (about 4.1M results per execution).jbr 6.6.0 (rubensworks/jbr.js#110, with sparql-benchmark-runner 5.5.0) adds
queryRunnerRecordTimestamps. This PR sets it tofirstin the WatDiv template:timestampscolumn holds the time to the first result, whichpsbr's query plots draw as their first-result marker. The plotted query times, fromtimeandtimes, are unchanged.all). Its queries return few results, so its outputs stay small.jbr 6.6.0 also brings rubensworks/jbr.js#108 to all three experiments:
jbr preparecreatesgenerated/itself, so Docker no longer creates it owned by root. That caused the EACCES error when preparing WatDiv.-fregenerates a sharedgenerated/once, instead of once per combination.Changes
package.json: all jbr packages go to^6.6.0in BSBM, WatDiv and LDBC SNB."queryRunnerRecordTimestamps": "first"in the template, and the combinations regenerated. BSBM's and LDBC SNB's combinations are unchanged.Checks
npm ciinstalls jbr 6.6.0 in all three experiments, andjbr validatepasses for each.queryRunnerRecordTimestamps: "first"for all 10 combinations.Generated by Claude Code