Lewati ke konten utama

Analytics

Bluefin

Systems active per day.

Bluefin :stable: accumulating dataBluefin :testing: accumulating dataBluefin :unknown: accumulating data

Bluefin daily active systems unavailable

No raptors reporting in, life finds a way

Bluefin Utah

Systems active per day.

Bluefin Utah :stable: accumulating dataBluefin Utah :testing: accumulating dataBluefin Utah :unknown: accumulating data

Bluefin Utah daily active systems unavailable

No raptors reporting in, life finds a way

Bluefin Classic (ublue-os/bluefin)

ublue-os/bluefin:stable, counted by ublue-os/countme. Metalink hits, not image check-ins.

Bluefin Classic: unavailableBluefin: accumulating data

Upstream count unavailable

The upstream badge could not be read.

Image × Stream Publication Matrix

Days since each published image last pushed to each promotion stream. One hue at four intensities, plus a glyph:

NominalWatchAlertUnknown

Image stream matrix unavailable

Reading the registry snapshot…

Streams: every image promotes :testing → :stable, which is the whole axis. Read from each repository’s execute-release.yml promotion matrix. The :gts and :latest tags still sit on some images as leftovers from retired schemes; nothing promotes through them, so they are not columns here.

Project Bluefin Image Family

Every image projectbluefin/common ships into, with the GHCR flavors each family publishes.

Bluefin

Flagship Workstation · Fedora
Active Tracking
  • bluefintesting —stable —
  • bluefin-nvidiatesting —stable —
Bluefin details →

Project Bluefin Dakota

Next-Gen BuildStream · GNOME OS / BuildStream 2
Alpha · Collecting
  • dakotatesting —stable —
  • dakota-nvidiatesting —stable —
  • dakota-gamingtesting —stable —
  • dakota-nvidia-gamingtesting —stable —
Project Bluefin Dakota details →

Bluefin Server

Image-Based Server · freedesktop-sdk 26.08
Alpha · DDI delivery
  • DDI + systemd-sysupdate delivery — no container stream
Bluefin Server details →

Update Churn & Compression Analytics​

Project Bluefin measures download byte delta, layer reuse efficiency, and compression statistics between consecutive stable releases.

Using Chunkah and the zstd-chunked container layer format, operating system updates are segmented into fine-grained package intervals so clients download only specific chunks containing changed packages.

Latest Fleet Churn
6.03GB
Across all active stable workstation releases
OCI Layer Reuse
30.3%
Shared layers cached on client bootc systems
Zstd:Chunked Adoption
77%
322 total package interval chunks
Tracked Images
3of 3
Images carrying at least one recorded release
OCI Layer Caching

Download Churn per Release

Bytes a client actually pulls for each release, one lane per image on a single 0–3,500 MB domain. Diamonds are baseline pulls: the first tag this pipeline tracked, which has no previous tag to diff against, so it carries the whole image rather than a delta.

Download churn per releaseLatest measured delta — Bluefin 479 MB. 10 measured deltas across 3 image lanes, all on one 0–3,500 MB domain.
Show the numbers
Download churn and baseline pull size per image and release date, in MB
Bluefin rolling median (5)Bluefin p50–p95 spreadBluefin download delta (MB)Bluefin baseline pull (MB)Project Bluefin Dakota download delta (MB)Project Bluefin Dakota baseline pull (MB)Project Bluefin Utah download delta (MB)Project Bluefin Utah baseline pull (MB)
2026-08-09703.3410.20000000000005478.9no datano datano datano datano data
2026-08-11868.7244.79999999999995703.3no datano datano datano datano data
2026-08-13868.7244.79999999999995671.1no datano datano datano datano data
2026-08-18868.7244.79999999999995868.7no datano datano datano datano data
2026-08-20858.52551113.5no datano datano datano datano data
2026-08-25826.8114.10000000000002940.9no datano datano datano datano data
2026-09-01no datano data858.5no datano datano datano datano data
2026-09-08no datano data769.7no datano datano datano datano data
2026-09-15no datano data763.4no datano datano datano datano data
2026-09-22no datano data826.8no datano datano datano datano data
2026-09-29no datano datano data3174.9no data3478.8no data2212.7

Percentile band withheld: a rolling p50 and p50–p95 band needs 5 consecutive measured deltas. Project Bluefin Dakota has 0 (5 more needed), Project Bluefin Utah has 0 (5 more needed). The band is drawn per lane as soon as that lane reaches 5.

Cache Hit Rate

Layer Reuse by Image and Release

Share of bytes already on disk when each release landed. One hue at four intensities, plus a glyph:

60%+ reused25–59% reusedunder 25% reusednot measured

Layer reuse by image and release10 of 33 image-by-release cells carry a measured reuse figure. Latest — Bluefin 84.9%.
Show the numbers
Layer reuse efficiency per image and release date
2026-08-092026-08-112026-08-132026-08-182026-08-202026-08-252026-09-012026-09-082026-09-152026-09-222026-09-29
Bluefin● 85%● 78%● 79%● 73%● 65%● 70%● 73%● 76%● 76%● 74%○ base
Project Bluefin Dakota——————————○ base
Project Bluefin Utah——————————○ base
Byte Composition

Cached vs Downloaded Bytes

Each release split into bytes served from the local layer cache and bytes pulled over the network, stacked to the image’s full size. Every lane shares one 0–3,500 MB domain; baseline tags are withheld because their split is not measured.

Cached, served from diskDownloaded over the network

Cached versus downloaded bytes per releaseLatest split — Bluefin 2,687 MB cached and 479 MB downloaded of 3,166 MB.
Show the numbers
Cached and downloaded megabytes per image and release date
Bluefin cached (MB)Bluefin downloaded (MB)Project Bluefin Dakota cached (MB)Project Bluefin Dakota downloaded (MB)Project Bluefin Utah cached (MB)Project Bluefin Utah downloaded (MB)
2026-08-092687478.9no datano datano datano data
2026-08-112462.6703.3no datano datano datano data
2026-08-132496.5671.1no datano datano datano data
2026-08-182299868.7no datano datano datano data
2026-08-202054.41113.5no datano datano datano data
2026-08-252228.8940.9no datano datano datano data
2026-09-012311.3858.5no datano datano datano data
2026-09-082404.2769.7no datano datano datano data
2026-09-152410.6763.4no datano datano datano data
2026-09-222348.1826.8no datano datano datano data
2026-09-29no datano datano datano datano datano data
Layer Format Migration

Compression Format State Lane

The layer format each release shipped in, with the count of layers already in zstd:chunked form out of the release’s total. One hue plus a glyph:

zstd:chunkedgzipno release

Compression format per image and release13 recorded releases carry a layer format. Latest — Bluefin gzip (0 of 74 layers), Project Bluefin Dakota zstd-chunked (120 of 120 layers), Project Bluefin Utah zstd-chunked (128 of 128 layers).
Show the numbers
Layer compression format per image and release date
2026-08-092026-08-112026-08-132026-08-182026-08-202026-08-252026-09-012026-09-082026-09-152026-09-222026-09-29
Bluefin▲ 0/74▲ 0/74▲ 0/74▲ 0/74▲ 0/74▲ 0/74▲ 0/74▲ 0/74▲ 0/74▲ 0/74▲ 0/74
Project Bluefin Dakota——————————● 120/120
Project Bluefin Utah——————————● 128/128
Per Image

Latest Release per Image

The current numbers behind every lane above, with the measured deltas as a sparkline on the shared 0–3,500 MB churn domain.

Bluefin

Flagship Workstation · :stable
gzip
Churn
479MB
Reuse
84.9%
Layers
74chunks
Total
3,166MB
Measured deltas · 10 of 11 releasesBluefin download churn, latest 479 MB across 10 measured deltas

Project Bluefin Dakota

Next-Gen Workstation · :stable
zstd-chunked
Churn
—MB
Reuse
—%
Layers
120chunks
Total
3,479MB
Measured deltas · 0 of 1 releasesaccumulating data

Project Bluefin Utah

Modular Workstation · :testing
zstd-chunked
Churn
—MB
Reuse
—%
Layers
128chunks
Total
2,213MB
Measured deltas · 0 of 1 releasesaccumulating data

Chunkah rechunks system updates into package-interval OCI layers. Shared layers require 0 download bytes during bootc updates. Source: GHCR OCI Manifests & Attestations · method oci-layer-diff-v1 · generated 2026-09-29.

Methodology, Privacy & Opt-Out

Counting Methodology​

Every Project Bluefin count comes from countme.projectbluefin.io

First-party Countme Service & Privacy Guarantees​

Project Bluefin Dakota and Utah images send a daily active-system ping from the projectbluefin-countme systemd timer to https://countme.projectbluefin.io/v1/ping. Other images do not send it.

  • What is sent: a single string, <image-name>/<image-flavor>:<stream>, where the stream is the booted image's tag (stable, testing, or unknown). Nothing else: no install age, architecture, machine ID, username, or persistent identifier.
  • How often: at most once per day per system, and never from a live ISO, installer, or container.
  • What is stored: one counter per UTC day and image. No per-system rows and no IP addresses. A day's count is the number of systems active that day, not distinct devices over time.

Opt-Out Instructions​

To stop Project Bluefin countme reporting now and across reboots, mask its systemd timer:

sudo systemctl mask --now projectbluefin-countme.timer

A mask of the previous bluefin-countme.timer or bluefin-countme.service units, and the /etc/projectbluefin/countme/disabled opt-out file, still stop reporting.

To disable upstream Fedora countme:

To disable Homebrew analytics:

brew analytics off

See the Homebrew analytics documentation for additional details.

Contributor Metrics​

For real-time development and organizational velocity metrics across all 15 factory repositories, see the Factory metrics view.

Upstream repository metrics for projectbluefin/bluefin are also tracked on Linux Foundation Insights.

Contributors to this page

  • Aelvryx
  • castrojo