nothing-but-datacenters · the public record

nothing
but datacenters

Data centers are the most physically demanding infrastructure of this moment — measured in gigawatts, in aquifers, in farmland converted to windowless halls. We have agreed to call them the cloud.

This work feeds one image of a data center back into an image model 43,200 times, each frame the input for the next. Thirty minutes, two channels. The work is on reillydonovan.com; this site is the record of how it was made.

A sample render, not the delivery encode. The finished encode comes from pass-08, which is still rendering.

1536×1344side-by-side, image left / text right24 fps768×1344 per channelthe bars are the host’s, not the work’s

Vertical, two channels side by side, 1536×1344. Most players letterbox it; this one is sized to the work.

pass 2 · sampled evenly, 0:00 to 30:00

Thirty of 4,090 stills, which themselves stand for 154,862 rendered frames. Scroll it, and open any one in place — arrow keys step through, escape closes. The arc runs sparse to saturated and closes where it opened; the whole gallery is 4,090 deep.

every pass on one axis · frame 1 to 43,200 · 0:00 to 30:00

frame 1 · 0:0021,600 · 15:0043,200 · 30:00

pass-011–6,319

pass-021–43,200

pass-03-rehearsal1–3,600

pass-04-rehearsal2–2,417

pass-05-rehearsal2–616

pass-06-rehearsal1 files

pass-07-rehearsal1–3,600

pass-082–10,485

verified by manifestobserved in the logno record

One pass is finished. One is still rendering. One was stopped and never resumed. The rest are rehearsals. Vertical ticks are chain breaks — frames rendered at full denoise, where the feedback loop is cut.

Statement

An image of a data center is fed back into an image model tens of thousands of times, each frame becoming the input for the next. Nothing is drawn by hand. The picture drifts — geometry loosening, structures giving way — and then, at intervals, snaps back. The model keeps recovering the building. It cannot stop producing the thing it was asked for.

Data centers are the most physically demanding infrastructure of this moment — measured in gigawatts, in aquifers, in farmland converted to windowless halls — and we have agreed to call them the cloud. That word does the work of making a building disappear. Here the disappearance is not a metaphor but a procedure, running at twenty-four frames per second, performed by the same class of system the buildings were raised to house.

Across thirty minutes the two channels begin from identical conditions and drift apart, each finding its own rhythm of collapse and recovery. What the work finally holds is not the image of a data center but its persistence: a form the machine returns to no matter how far the picture strays.

Pass 2, measured

43,200frames, pass 2

30:00runtime

2channels

768×1344per channel

70 h 22 mgpu logged

5.87 sper frame

One GPU, one continuous feedback chain, roughly 5.9 seconds a frame. The pass 2 record holds the rest of it — every run, every driver hash, and the things the record does not claim to know.

Not published

per-frame sampler seeds

The render log records the prompt, sampler seed and applied denoise of every frame. That is excellent provenance and also a complete reproduction recipe. The schedule and the summary statistics are here; the seeds are available on request.

the masters

The project is 244 GB and the 30-minute ProRes master is 32 GB. Frames and masters are named and sized throughout this site, never copied into it.

The record

Passes8 recorded · frames, runs, drivers, and what is verified Treatments12 recorded · derived work, not passes Prompt architecture9 recipes · schedule and vocabulary Design systemhow the record is drawn, and why

nothingbut datacenters

Statement

Pass 2, measured

Not published

The record

nothing
but datacenters