History graphs

CI metrics are stored on the metrics-history branch. The charts below load those live series.

Doxygen warnings

CI records the number of Doxygen warnings produced when the documentation is built.

Raw JSON: doxygen_warnings.json.

Compile peak RSS (top 10 files)

CI records per-translation-unit compiler peak RSS. The chart keeps only the top 10 files of each commit: a file that drops out of that ranking is omitted at that date (null y, connectgaps: false).

Raw Plotly JSON: compile_memory_top10.json.

The org website (https://shamrock-code.github.io/) is same-origin with the published Sphinx docs, so it can embed this chart with:

<iframe
  src="https://shamrock-code.github.io/Shamrock/sphinx/_static/doxygen_warnings.html"
  title="Doxygen warning count over time"
  width="100%"
  height="600"
  style="border: none;"
></iframe>

Build time

CI records ClangBuildAnalyzer compile times: the sum of frontend parsing and backend codegen across translation units. That is cumulative compiler work, not wall-clock time. The right axis shows how many translation units were profiled. See Profiling build performance / time.

Raw JSON: build_time_total.json.

The org website can embed this chart with:

<iframe
  src="https://shamrock-code.github.io/Shamrock/sphinx/_static/build_time_total.html"
  title="Build time and translation units over time"
  width="100%"
  height="640"
  style="border: none;"
></iframe>

Parse time (top 10 files)

CI records ClangBuildAnalyzer frontend parse times per translation unit. The chart keeps only the top 10 files of each commit: a file that drops out of that ranking is omitted at that date (null y, connectgaps: false). Object-file paths are mapped back to source paths. See Profiling build performance / time.

Raw Plotly JSON: parse_time_top10.json.

The org website can embed this chart with:

<iframe
  src="https://shamrock-code.github.io/Shamrock/sphinx/_static/parse_time_top10.html"
  title="Top 10 files that took longest to parse"
  width="100%"
  height="700"
  style="border: none;"
></iframe>

Codegen time (top 10 files)

CI records ClangBuildAnalyzer backend codegen time per translation unit. The chart keeps only the top 10 files of each commit: a file that drops out of that ranking is omitted at that date (null y, connectgaps: false). Object-file paths are mapped back to source paths. See Profiling build performance / time.

Raw Plotly JSON: codegen_time_top10.json.

The org website can embed this chart with:

<iframe
  src="https://shamrock-code.github.io/Shamrock/sphinx/_static/codegen_time_top10.html"
  title="Top 10 codegen time over time"
  width="100%"
  height="700"
  style="border: none;"
></iframe>

Function sets (top 10 compile / optimize)

CI records ClangBuildAnalyzer function-set compile/optimize times. The chart keeps only the top 10 function sets of each commit: a set that drops out of that ranking is omitted at that date (null y, connectgaps: false). See Profiling build performance / time.

Raw Plotly JSON: function_sets_top10.json.

The org website can embed this chart with:

<iframe
  src="https://shamrock-code.github.io/Shamrock/sphinx/_static/function_sets_top10.html"
  title="Top 10 function sets compile / optimize time over time"
  width="100%"
  height="700"
  style="border: none;"
></iframe>

Lines of code

CI counts lines in tracked source files, excluding git submodules. Exclusive partitions (code, examples, doc) sum to all. Nested shammodels/* counts are subsets of code, not extra buckets. File-type totals sum the exclusive partitions only. Both y-axes use a log scale so small series stay visible next to the totals.

Raw JSON: loc.json.

The org website can embed this chart with:

<iframe
  src="https://shamrock-code.github.io/Shamrock/sphinx/_static/loc.html"
  title="Lines of code over time"
  width="100%"
  height="900"
  style="border: none;"
></iframe>