ComfyICU / RTX 5090 cold-start analysis

Storage path & cold start

Why nominally similar RTX 5090 hosts load models differently—and how to separate pre-run screening evidence from diagnostics measured inside the workload.

Current interpretation

Validate the complete path, not the SSD label

Cold-start variance follows the path that actually delivers model bytes to ComfyUI: drive, negotiated link, filesystem/container layers, host state and loader access pattern.

The owned nodes use one 2 TB 9100 Pro model drive plus a separate OS drive, without model-cache RAID. The repeated application result and physical-read evidence—not a synthetic threshold—accept each node.

—buffered fio vs MiniMax cold penalty—the strongest current independent screening relationshipLoading the in-workload diagnostic and dataset timestamp…
Loading DuckDB analysis…
Evidence hierarchy

Read the measurements in this order

Each layer answers a different question. Stronger proximity to the timed run also means less independence from the outcome.

Prior

Specification and Vast score

—

Useful before rental, but it does not observe the mounted path used by ComfyUI.

Independent screen

Buffered fio after invalidation

—

Best current independent proxy because it traverses more of the real buffered path.

In-run diagnosis

Active workload read rate

—

Explains where elapsed time went, but is measured inside the timed cold process and cannot screen an untested host.

Admission rule: only the complete repeated ComfyUI workload accepts a node. Independent probes help find a bad path; in-run diagnostics help explain a failed result.
The central multivariable result

The broad storage signal weakens inside healthy link classes

Spearman correlation with MiniMax cold−warm penalty. Negative means faster storage tends to accompany a smaller penalty.

—
MeasurementAll single pathsExposed NVMePCIe 5.0 x4PCIe 4.0 x4
Apparent contradictions explained

Why a slower probe can accompany a smaller penalty

The standalone reader and ComfyUI do not always realize the same delivery rate. One additional host is a noisy accelerator/runtime outlier.

Keep raw time visible: machine 45827 has a small incremental penalty but extremely slow cold and warm wall times. A small `cold − warm` value does not necessarily mean fast service.