A child forge's disk bandwidth is capped by its size

A child forge's cell shares the parent's disk. io.weight only orders the queue, so one busy child could still starve the parent's database and its neighbours. Each child's cell now gets io.max on the disk under the forge's data, sized by the child's size (#10854).

SizeReadWriteRead ops/sWrite ops/s
small50 MiB/s25 MiB/s1000500
medium100 MiB/s50 MiB/s20001000
large200 MiB/s100 MiB/s40002000

MAJ:MIN rbps=… wbps=… riops=… wiops=…. The device is the whole disk under the child's directory in the forge's data (a partition is walked up to its disk through /sys/dev/block).

cells/, where the data sits on no block device (tmpfs, overlay, a network mount), or where the kernel refuses the device. The cell still starts; only io.weight orders it then. The cell's cgroup result says which (ioCapped).

SIZE_IO in src/spawn/sizes.ts. To tune: run fio (or dd oflag=direct) against the data volume on the host to learn what the disk sustains, then keep the largest size's cap well under it so the parent always has headroom. A new cap applies when a child's cell next starts. Watch cells/<child>/io.stat against io.max to see whether a child is pinned at its cap.

gets io.max only where io is delegated).

↑↓ navigate ↵ open ⌘↵ its app esc close

Keyboard shortcuts

Docs