Show Spent Time (🚫Deprecated)

Let's be upfront: this node is deprecated. Easy-Use marks it as such right in its category (EasyUse/🚫 Deprecated), so if you're starting a fresh workflow, don't build around it. It's worth a page anyway, because it was one of the very first nodes in the whole pack - it landed back in December 2023 - and you'll still find it living in older graphs and tutorials, so it helps to know what it did and what to use instead.

What it did

easy showSpentTime reads an Easy-Use pipe after a sampling pass and displays, right on the node, how long the run took - split into the diffusion (sampling) time and the VAE decode time. That's it. No image, no data output; it's a pure readout node. The idea was to give you a quick "why is this slow" glance without leaving the canvas: if VAE decode is eating half your time, that points somewhere very different than sampling being slow.

The inputs and outputs that matter

There's exactly one input and no outputs:

• pipe - the pipe coming out of your sampler. That pipe carries the timing information the node reads and prints. Wire your easy fullkSampler (or another Easy-Use sampler) pipe into it.

Because it has no output slots and is an output node, it's a terminal - it just sits there and shows you the numbers. There's nothing to wire onward.

Installing it

It comes with the pack, so there's no separate download. If you're on an older ComfyUI-Easy-Use the node is present; on newer ones it's in the Deprecated group. Install the pack via ComfyUI Manager (search ComfyUI Easy Use, restart) or:

cd ComfyUI/custom_nodes
git clone https://github.com/yolain/ComfyUI-Easy-Use

Install requirements and restart.

What to use instead

Since this node was written, ComfyUI itself grew much better at surfacing timing. The console/log already prints per-node execution time, and the frontend shows run duration, so the specific value showSpentTime added - a diffusion-vs-VAE split on the canvas - is mostly redundant now. That's why it got deprecated rather than deleted: it still runs, it just isn't the recommended way to profile a workflow anymore.

If you inherited a workflow that has it wired in, you don't have to rip it out - a deprecated node isn't a broken node, and it won't hurt anything. But if it ever throws an error after a ComfyUI or frontend update, that's your cue: delete it rather than debug it. For actually understanding where your time goes, watch the ComfyUI console during a run, or lean on the built-in timing the frontend already gives you. Deprecated means the maintainer has stopped caring about this one, and you can too.