Performance

How long glsec takes to scan one large pipeline: 2,000 jobs with extends: and !reference chains, anchors and long scripts, about 650 KB, far bigger than real pipelines so that slow code shows. Every release since v1.0.0 and every change to main is measured on the same file, each time as the median of seven runs. Every dot links to its commit; hover for the details.

The time grows with the rules: each release checks more, from 64 rules in v1.3.0 to 89 in v1.24.1. The releases were measured one after another on the same machine, so their times compare.

Every push to main runs on whatever GitHub runner it gets, and their speed varies by 10 to 30% or more. So each push also measures the latest release in the same job, taking turns, and the chart shows the ratio: below 1.0 is faster than the release. The latest commit, 251f202, takes 0.51 × v1.24.1.

Allocations don't depend on the machine; they are recorded for commits on main.

Measured by the benchmark history workflow; the records and the input are on the benchmarks branch.