Jimeng Progress Test

This node exists to make a progress bar move. That's its job, and if that sounds pointless, you're not the target audience - it's a development tool the pack author uses to test the front-end progress styling, shipped alongside the real nodes because it's handy to have around. It doesn't generate anything and it doesn't call the API. The README doesn't even talk about it; it's an under-the-hood utility that leaked into the node list.

You'll probably never need it in a real workflow. But it has one genuinely useful party trick.

How it works

Give it duration_seconds and steps, run it, and it simulates a generation's progress events locally - ticking a progress bar over the simulated time with the right number of steps, no network involved. Useful if you're building your own UI around this pack, styling ComfyUI's progress output, or testing how workflows behave when something takes a while. The output is just a string saying it finished.

Here's the trick: the client input is optional, and so is test_model. If you actually wire a Jimeng API Client in and pick a real model, the node stops faking it. It queries the Ark API for that model's estimated generation time and pulls your actual task history for the same model and resolution, then returns a JSON report: estimated_time, estimation_method, and up to 20 real historical samples with how long each task actually took. That's a free way to answer "how much does a 1080p clip at 10 seconds actually cost me in wall-clock time" before you commit to a batch.

The inputs that matter

• duration_seconds - simulated length, 1 to 300.
• steps - how many progress ticks, 1 to 600.
• client (optional) - attach the API client to flip into estimation mode.
• test_model - which model to estimate for (default "None" stays fully offline).
• test_resolution - the resolution to estimate against, default 720p.

Output

• response - a string; either "Jimeng Progress Test Finished" or, in estimation mode, the JSON report.

Installing and when to ignore it

Install is the pack-standard route (ComfyUI Manager or git clone https://github.com/fkxianzhou/ComfyUI-Jimeng-API into custom_nodes, restart). It's marked dev-only in the source, so don't expect it in the docs - and if you're a normal user, honestly, leave it in the palette. It won't hurt you.

The one scenario where it earns its keep: you're about to run a big batch of video generations and you want a cost-in-time estimate from your own key's history. Wire in a client, pick your model and resolution, and read the report. Everything else this node does is for people who stare at CSS for a living.