146 lines
3.5 KiB
Markdown
146 lines
3.5 KiB
Markdown
# Performance Report: 4.2.31
|
|
|
|
**Generated:** 2026-01-28T22:17:41Z
|
|
**Pipeline:** [#13303](https://git.unturf.com/engineering/unturf/un-inception/-/pipelines/13303)
|
|
|
|
## Summary
|
|
|
|
| Metric | Value |
|
|
|--------|-------|
|
|
| Total Tests | 704 |
|
|
| Passed | 701 |
|
|
| Failed | 3 |
|
|
| Pass Rate | 99.5% |
|
|
| Languages | 43 |
|
|
| Avg Duration | 74s |
|
|
| Slowest | go (106s) |
|
|
| Fastest | erlang (43s) |
|
|
|
|
---
|
|
|
|
## Test Duration by Language
|
|
|
|
The primary performance metric - how long each language takes to run its full test suite (15 tests per language).
|
|
|
|
|
|
|
|
**Key observations:**
|
|
- **GO** and **RUST** are outliers at 90+ seconds
|
|
- Most languages cluster between 20-40 seconds
|
|
- Compiled languages (red) tend to be faster than interpreted (blue)
|
|
- **ERLANG** is the fastest at 43 seconds
|
|
|
|
---
|
|
|
|
## Compiled vs Interpreted
|
|
|
|
Comparing performance between compiled languages (C, Go, Rust, etc.) and interpreted languages (Python, Ruby, JavaScript, etc.).
|
|
|
|
|
|
|
|
**Findings:**
|
|
- 20 compiled languages vs 22 interpreted
|
|
- Compiled languages have lower median execution time
|
|
- Interpreted languages show more variance (wider spread)
|
|
- The white diamond marks the mean for each category
|
|
|
|
---
|
|
|
|
## Duration Distribution
|
|
|
|
Histogram showing how test durations are distributed across all 43 languages.
|
|
|
|
|
|
|
|
**Distribution analysis:**
|
|
- Most languages complete in 20-35 seconds (the peak)
|
|
- Mean (green dashed) and median (blue dotted) are close together
|
|
- Long tail on the right from slow outliers (go, rust)
|
|
|
|
---
|
|
|
|
## Speed Leaders
|
|
|
|
Side-by-side comparison of the 10 slowest and 10 fastest languages.
|
|
|
|
|
|
|
|
**Slowest (left):** GO, RUST, FORTH, SCHEME, GROOVY
|
|
**Fastest (right):** ERLANG, RAKU, PROLOG, CSHARP, DOTNET
|
|
|
|
---
|
|
|
|
## Queue vs Execution Time
|
|
|
|
Scatter plot showing the relationship between CI queue wait time and actual test execution time.
|
|
|
|
|
|
|
|
**Notes:**
|
|
- Queue time is how long the job waited for a runner
|
|
- Most jobs had similar queue times (clustered vertically)
|
|
- Outliers labeled - go and rust took longest to execute regardless of queue time
|
|
|
|
---
|
|
|
|
## Dashboard
|
|
|
|
Summary dashboard combining key metrics and visualizations.
|
|
|
|
|
|
|
|
---
|
|
|
|
## Raw Data
|
|
|
|
### Per-Language Performance
|
|
|
|
| Language | Status | Duration |
|
|
|----------|--------|----------|
|
|
| go | Passed | 106s |
|
|
| rust | Passed | 105s |
|
|
| forth | Passed | 103s |
|
|
| scheme | Passed | 94s |
|
|
| groovy | Passed | 94s |
|
|
| crystal | Passed | 92s |
|
|
| clojure | Passed | 92s |
|
|
| c | Passed | 92s |
|
|
| cpp | Passed | 91s |
|
|
| commonlisp | Passed | 91s |
|
|
| zig | Passed | 89s |
|
|
| deno | Passed | 89s |
|
|
| java | Passed | 88s |
|
|
| powershell | Passed | 87s |
|
|
| awk | Passed | 87s |
|
|
| cobol | Passed | 85s |
|
|
| d | Passed | 82s |
|
|
| kotlin | Passed | 81s |
|
|
| tcl | Passed | 79s |
|
|
| fortran | Passed | 78s |
|
|
| typescript | Passed | 71s |
|
|
| python | Passed | 70s |
|
|
| ruby | Passed | 67s |
|
|
| php | Passed | 67s |
|
|
| julia | Passed | 67s |
|
|
| haskell | Passed | 67s |
|
|
| javascript | Passed | 64s |
|
|
| v | Passed | 63s |
|
|
| nim | Passed | 63s |
|
|
| fsharp | Passed | 63s |
|
|
| elixir | Passed | 63s |
|
|
| dart | Passed | 63s |
|
|
| bash | Passed | 63s |
|
|
| ocaml | Failed | 63s |
|
|
| r | Passed | 61s |
|
|
| objc | Passed | 61s |
|
|
| lua | Passed | 61s |
|
|
| perl | Passed | 59s |
|
|
| dotnet | Passed | 55s |
|
|
| csharp | Passed | 55s |
|
|
| prolog | Passed | 52s |
|
|
| raku | Failed | 52s |
|
|
| erlang | Failed | 43s |
|
|
|
|
---
|
|
|
|
*Report generated by UN Inception CI pipeline*
|