Samples Passthrough (Stat System)

Per the README, this node "logs RAM, VRAM, and disk usage to the console." That's the entire function, and it's genuinely useful in exactly the situation where you'd reach for it: a long, memory-heavy graph that's running out of headroom somewhere, and you need to know where, not just that it eventually happens.

What it actually does to your samples

Nothing. That's the point of "passthrough" in the name - you wire your SAMPLES (latent) through this node exactly like you would through any other latent node in the chain, and it hands the identical value straight back out the other side, unmodified. The entire value of the node is a side effect: at the moment execution passes through it, it prints your machine's current RAM, VRAM, and disk usage to the console. The samples themselves never change.

Why you'd drop one into a graph

Diagnosing where a big workflow actually runs out of memory. A single "ran out of VRAM" error at the end of a long chain - upscale, detail pass, a second model load, a video interpolation step - tells you it happened somewhere, not where. Chain a few of these stat nodes at different points in the graph (before and after the heavy upscale, before and after loading a second checkpoint) and you get a running log of memory climbing through your pipeline, which turns "somewhere in this workflow" into "right here, between these two nodes." It's a cheap, no-code way to profile a graph without reaching for external tooling.

The inputs and outputs that matter

One SAMPLES input, the identical SAMPLES as output - unchanged, just relayed through. There's nothing to configure; the node's only real behavior is the console log it produces as it executes.

Installing it

ComfyUI Manager: search "WAS Node Suite," install, restart. Manually:

cd ComfyUI/custom_nodes
git clone https://github.com/WASasquatch/was-node-suite-comfyui

install requirements.txt against your ComfyUI Python, restart. No model, and the system-stat reads it uses are lightweight - this isn't a node that adds meaningful overhead of its own.

Common issues & troubleshooting

I don't see any output anywhere. The stats print to the console, not to a widget on the node itself - there's nothing visible in the graph UI to look at. You need to actually be watching the terminal or log window ComfyUI is running in to see anything. If you're on a hosted or headless setup, confirm your platform actually surfaces stdout somewhere you can view it; if it doesn't, this node is quietly logging into the void and won't help you at all in that context.

The samples look unaffected - is that right? Yes, by design. This is purely a diagnostic tap, not a processing step. If your graph's output changed after adding this node, something else changed too - the node itself doesn't touch the data.

Whole pack won't import. Pack-level, not this node. WAS Node Suite has been unmaintained since the author marked it retired in December 2023, and the recurring failure since is the entire suite throwing "Import Failed" after a ComfyUI update from a pinned dependency clash. Reinstall requirements.txt against the correct, embedded Python interpreter and restart.