walleby Publifye

How we keep our servers from filling up

Every Publifye server runs one small daemon, walle. It measures its own disks, memory and pressure every fifteen minutes, cleans up by rule, and reports what it did. These are the fleet's figures, aggregated and rounded; nothing here identifies a server.

1
server watched
each runs one walle daemon
22 %
of disk space kept free
across the fleet, newest full day
93 %
reporting coverage
share of time the servers reported in; not uptime
0 GB
cleaned in the last 7 days
68 GB
cleaned in the last 30 days
287 GB
cleaned since 10 Oct
history starts then
3.1 h
typical time from alert to fixed
median of 2839 closed alerts (warn or critical)

Data cleaned: moved to walle's trash, deleted outright by a rule, or freed by the emergency ladder, summed; emptying the trash is not counted again.

Data cleaned per month

December 2025: no dataJanuary 2026: no dataFebruary 2026: no dataMarch 2026: no dataApril 2026: no dataMay 2026: no dataJune 2026: no dataJuly 2026: no dataAugust 2026: no dataSeptember 2026: no datano data0 GB100 GB200 GB300 GB400 GB500 GBDecMarJunNovOctober 2026: 287 GB
December 2025: no dataJanuary 2026: no dataFebruary 2026: no dataMarch 2026: no dataApril 2026: no dataMay 2026: no dataJune 2026: no dataJuly 2026: no dataAugust 2026: no dataSeptember 2026: no datano data0 GB100 GB200 GB300 GB400 GB500 GBDecFebAprJunAugNovOctober 2026: 287 GB
December 2025: no dataJanuary 2026: no dataFebruary 2026: no dataMarch 2026: no dataApril 2026: no dataMay 2026: no dataJune 2026: no dataJuly 2026: no dataAugust 2026: no dataSeptember 2026: no datano data0 GB100 GB200 GB300 GB400 GB500 GBDecFebAprJunAugNovOctober 2026: 287 GB
December 2025: no dataJanuary 2026: no dataFebruary 2026: no dataMarch 2026: no dataApril 2026: no dataMay 2026: no dataJune 2026: no dataJuly 2026: no dataAugust 2026: no dataSeptember 2026: no datano data0 GB100 GB200 GB300 GB400 GB500 GBDecFebAprJunAugOctNovOctober 2026: 287 GB
December 2025: no dataJanuary 2026: no dataFebruary 2026: no dataMarch 2026: no dataApril 2026: no dataMay 2026: no dataJune 2026: no dataJuly 2026: no dataAugust 2026: no dataSeptember 2026: no datano data0 GB100 GB200 GB300 GB400 GB500 GBDecJan 26FebMarAprMayJunJulAugSepOctNovOctober 2026: 287 GB

Bytes walle moved to its trash, deleted outright by a rule, or freed in an emergency, summed per month across every server; emptying the trash is not counted again, because those bytes were counted when they were moved. A sum, never an average. These are calendar months; rolling-window totals differ. November is drawn hollow: the month is not over.

How it works, and why

Rules, then a trash, then a purge

walle cleans only what a written rule names, such as build caches that have grown past their cap. Some cache rules delete directly, where the cache rebuilds itself. The rest go to walle's trash first and are purged for good only once they have sat there long enough to be missed, so a mistake there can be undone for days.

An emergency ladder before a disk can fill

If a disk heads for full faster than the daily clean can keep up, walle climbs a ladder of increasingly firm, pre-written steps, so the server does not reach the point where nothing can write. Every step is recorded.

Alert once, again only if worse

When something needs a person, walle says so once. It speaks again only if the problem gets worse or comes back after it was fixed. An alert that repeats every few minutes teaches people to stop reading alerts.

Backups never on the same disk

A backup on the disk it protects is lost with it. Copies go to another disk, and the history behind these figures is also kept offsite.

One daemon per server

One walle per server, owning that server's disks. Two cleaners on one disk would fight, and nobody could say which one did what.

Honest numbers

Figures here are sums and medians, never averages: an average hides the one bad day. Coverage is the share of time the servers reported in, not a claim about uptime. A gap is shown as a gap.