Repository navigation
Website: add the Complexity metric - #2493
Merged
Merged
Conversation
Complexity is the zstd-compressed size of all the scripts and configs in a system's directory (install, load, start, stop, query, the Python and Expect scripts they invoke, etc.), with full-line comments, blank lines, and redundant whitespace removed. Queries, table definitions, results, docs, and the shared driver in lib/ are not counted. It is calculated in generate-results.sh; PR previews reuse the values of the base branch. Systems without the install script and cloud services are excluded, as their setup is not scripted. With this metric, each system is shown once, as it does not depend on the machine. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
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.
This came up during the conversation with @toschmidt at Open House Munich.
Adds the Complexity metric: how much code is needed to run the benchmark for a system. It is the byte size of the zstd-compressed (
-19) concatenation of all the tracked text files in the system's directory —install,load,start,stop,query,check,benchmark.sh, the Python/Expect/etc. scripts they invoke, configs, and generated code — with full-line comments (including shebangs), blank lines, and redundant whitespace removed.Not counted:
results/,*.json,*.md,*.sql(queries and DDL),*.txt, lock files, and the shared driver inlib/(the same for most systems, ~8.5 KB compressed, it would dominate the differences).generate-results.sh: computes the value once per system directory and adds thecomplexityfield to each entry. Systems without theinstallscript (with a manual procedure) getnull.index.html: a new metric selector and a row in the detailed comparison. Cloud services are excluded. Each system is shown once (by its latest result), without the machine, as the value does not depend on it. It is not included in the Combined score.results_preview.py: PR previews do not run or read the PR's scripts, so they reuse the values fromdata.generated.jsof the base branch.Preview: https://pastila.nl/?005fb6bd/65e94611aacde4c3ea1dc5a519479922.html.gz
data.generated.jswill be rebuilt by the bot.🤖 Generated with Claude Code