cedana / blog · field reports & engineering deep-dives

Writing from the
cedana team.

Engineering notes, benchmarks, and field reports covering how we build the automation layer for AI factories.
All posts · 99

insights from the team.

Field reports, engineering deep-dives, and benchmarks from the Cedana team.

Cedana. Blueprint of a conveyor belt with rollers running from a cloud outline on the left to a tall rack on the right. Four crates ride the belt, each with a small glyph on its face: a heartbeat line, three stacked bars, three coins, a ticked page. The first three carry a small grey tag on their lids; a grey dashed arrow above the belt points toward the rack.Sovereignty has a bill: the transferred duties and the availability math
· Cedana Editorial

Sovereignty has a bill: the transferred duties and the availability math

Size the availability responsibilities of running inference on your own hardware, including spare capacity, recovery time and a single node's outage allowance.

read →
Cedana. Blueprint of a large square tank outlined in ink, its lower half filled dark grey with faint horizontal lines, a dashed line across its surface, and the upper half stacked with fifteen thin blue slabs, the topmost brighter, with a row of small circles queued at its right edge and an arrow pointing in.Your KV cache now rivals your weights
· Cedana Editorial

Your KV cache now rivals your weights

Calculate KV cache bytes from model configuration, precision and context length, then estimate how many live sessions fit after the weights are loaded.

read →
Cedana. Blueprint of two documents side by side. The left carries a large bold cross beside a solid black block at its top and nine lines beneath, three of them solid with ticks and six dashed, with the sixth ringed in dashed red. The right carries two small ruled boxes at its top and nine solid lines each with a blue tick.How to read a checkpoint benchmark
· Cedana Editorial

How to read a checkpoint benchmark

Evaluate checkpoint benchmarks using nine disclosures, from capture scope and clock boundaries to storage, repeated runs and performance after restoration.

read →
Cedana. Blueprint of a large outlined box holding six horizontal slots. Five slots are filled from the left with pale-blue bars of different lengths; the fifth slot is empty. Outside the box on the left, three short dark grey bars are stacked, and a blue arrow leads from the top one into the empty slot.The engine layer: batching, caching, and configuration as a commitment
· Cedana Editorial

The engine layer: batching, caching, and configuration as a commitment

Understand how continuous batching, paged KV memory and prefix caching affect serving performance, and why changing a worker's regime means launching a new one.

read →
Cedana. Blueprint of two pools of four workers, marked prefill and decode. In the prefill pool each worker holds a short grey bar; grey dashed arrows cross to the decode pool, where each worker is stacked with blue slabs to a different height. From the tallest a blue dashed arrow leads right to a dashed outline holding the same slabs in pale blue, above a save icon marked checkpoint.Does disaggregated serving remove the need to move GPU workers?
· Cedana Editorial

Does disaggregated serving remove the need to move GPU workers?

See why separating prefill and decode does not make serving workers stateless, and what moving a worker means for its KV cache, sessions and startup cost.

read →
Cedana. Blueprint of two GPU cards side by side, each holding three horizontal bars: a dark bar of equal length in both, a blue bar noticeably shorter on the left card than on the right, and a second blue bar shorter still on the left. Below the left card a block of six parallel lines points up into it; below the right card a row of six blue dots points up into it; a red dashed line between the two is struck through.H100 for prefill, H200 for decode: the mismatch you pay for twice
· Cedana Editorial

H100 for prefill, H200 for decode: the mismatch you pay for twice

Compare H100 and H200 memory and compute for prefill and decode. Account for cache-transfer cost and why moving across GPU models still requires a cold start.

read →
Cedana. Blueprint of two rows of eight outlined boxes, each box holding four small tiles. In the top row one tile per box is blue and seven small arcs hop from box to box across the whole row. In the bottom row all four tiles are blue in only the fourth and fifth boxes, joined by a single arc, and every other tile is pale grey.Expert placement in a mixture-of-experts deployment is a systems decision
· Cedana Editorial

Expert placement in a mixture-of-experts deployment is a systems decision

Separate a model router's expert choices from the deployment layout you control. Review expert placement, attention parallelism and communication overlap.

read →
Cedana. Blueprint of a tall server rack holding eighteen trays of four grey GPU cells, with one cell in the upper middle filled red and struck out. A bracket down the rack's left side spans its full height. To the right, a long grey bar and beneath it a very short blue bar beside a saved-state icon.One GPU fails and 71 healthy GPUs wait
· Cedana Editorial

One GPU fails and 71 healthy GPUs wait

Understand how one failure stalls a tensor-parallel NVL72 workload, how recovery consumes healthy GPU-hours, and where published measurements stop.

read →
Cedana. Blueprint of five small glyphs down the left, a rising bar chart with a red top bar, a thermometer with a red column, an envelope, four scattered empty squares, and a calendar tile, each joined by a grey dashed wire to one blue ring at the centre holding a saved-state icon. From the ring one solid blue arrow leads to a node holding a blue block.Five fleet signals, five policies: from alert to automatic action
· Cedana Editorial

Five fleet signals, five policies: from alert to automatic action

Connect GPU health, thermal, reclaim, fragmentation and maintenance signals to workload-preserving actions. See which triggers ship and which remain designs.

read →
Cedana. Blueprint of three machines. A small one on the left holds one solid blue square. A wider one in the middle holds eight solid blue squares on a pale-blue tray. On the right three grey dashed machines each hold four dashed squares, linked by short dashed lines and spanned by one dashed bracket above them.Does multi-node checkpointing ship today?
· Cedana Editorial

Does multi-node checkpointing ship today?

Distinguish a workload moving between nodes from one spanning nodes. See Cedana's shipped single-node coverage and the multi-node tier still in design partnership.

read →
Cedana. Blueprint of a plot with a straight line falling from the upper left to the lower right across log axes. Two solid blue points sit on its upper half and two hollow dashed blue points on its lower half, the last one ringed in red near the bottom. A grey dashed horizontal line crosses the plot at the height of the second point.GPU failure frequency scales with the fleet, not the on-call rotation
· Cedana Editorial

GPU failure frequency scales with the fleet, not the on-call rotation

Use published cluster studies to understand how GPU job interruptions scale, distinguish measurements from projections, and estimate your own fleet's rate.

read →
Cedana. Blueprint of the same GPU card drawn three times down the left. The first is cut by six vertical walls into seven slices holding grey blocks of different heights, with a dashed empty card to its right. The second holds three overlapping translucent blocks with a red crack running through them, and a box to its right of three red dashes. The third is filled by one solid blue block, with a row of three blocks to its right, grey, blue, grey, separated by saved-state icons.Sharing GPUs without fixed MIG slices
· Cedana Editorial

Sharing GPUs without fixed MIG slices

Compare MIG, time-slicing, MPS and serial sharing through checkpoints. Understand isolation, fixed slice sizes and the save-and-restore cost of switching jobs.

read →

Showing 37–48 of 99 posts