Skip to content

Conversation

@davidgumberg
Copy link
Collaborator

@davidgumberg davidgumberg commented Feb 13, 2025

I don't think the current arrangement of results.json quite makes sense, hoping this doesn't break anything

@davidgumberg davidgumberg force-pushed the ZZZ-benchcoin-hyper-params branch from 96e0d35 to cba9c07 Compare February 13, 2025 23:41
Comment on lines 123 to 125
--command-name "base (${base_commit})" \
--command-name "head (${head_commit})" \
"taskset -c 2-15 chrt -o 0 ${BINARIES_DIR}/{commit}/bitcoind -datadir=${TMP_DATADIR} -connect=${connect_address} -daemon=0 -prune=10000 -chain=${chain} -stopatheight=${stop_at_height} -dbcache=${dbcache} -printtoconsole=0" \
-L commit "base,head"
"taskset -c 2-15 chrt -o 0 ${BINARIES_DIR}/{branch}/bitcoind -datadir=${TMP_DATADIR} -connect=${connect_address} -daemon=0 -prune=10000 -chain=${chain} -stopatheight=${stop_at_height} -dbcache=${dbcache} -printtoconsole=0" \
-L branch "base,head" \
-L commit "${base_commit},${head_commit}" # not used in the hyperfine command, but squeezing some more detail into the results.json

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Needing to change this in two places already feels silly. I did wonder whether instrumented/un-instrumented should be two scripts or one (with more if branches), and felt that two probably made more sense, but now I'm not so sure...

@github-actions github-actions bot force-pushed the master branch 7 times, most recently from c556197 to 7862a78 Compare February 22, 2025 03:21
@github-actions github-actions bot force-pushed the master branch 4 times, most recently from 607732d to e0dab54 Compare March 4, 2025 03:28
@github-actions github-actions bot force-pushed the master branch 6 times, most recently from 3b99594 to 4098c1c Compare March 10, 2025 03:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants