Plan recovery around an interrupted write
Filesystem recovery and application recovery protect different things on an unattended edge computer.
A publication about the hardware behind local AI.
Essays and guides, organised by their coverage period.
Retrospective essays are grouped by the month they cover. They were written and added on November 2, 2026; that is the publication date shown on each article.
Filesystem recovery and application recovery protect different things on an unattended edge computer.
Connect startup, readiness and restart policy to the application’s actual state.
Accepted requests, waiting requests and rejected requests need explicit limits before throughput is useful.
A runtime profile can turn a vague CPU complaint into a testable performance question.
Compressed swap can change a workload’s failure behaviour, so evaluate responsiveness alongside memory use.
Measure the time to a usable application before using an SSD’s headline transfer rate as an explanation.
Use the assembled system and a sustained task to decide whether a thermal design has enough margin.
A reproducible image needs a deliberate replacement process to stay useful.
Preserve preprocessing and expected outputs before treating model conversion as complete.
Weights, generation state and the rest of Linux need separate entries in a small computer’s memory budget.
A stage-by-stage latency budget makes the original AI HAT+ easier to assess for a specific vision job.
Treat the Super update as a configuration change whose benefits depend on the rest of the system.