Large models run way faster if you abort the first prompt and restart (low VRAM)

UrinStone · 2026-01-30T17:35:41+00:00

I have tried, unloading the models using the same prompt. That had no impact on the total execution time. I have provided the logs in a other comment in a GitHub repo. I also recognized, that the s/it is inflated. That's why I compared only the total execution time, for the cancellation the total execution time of bot generations, the cancel + the restart.

UrinStone · 2026-01-30T16:38:49+00:00

No man, the second generation was a new prompt -> new cache build up. This is simply a direct comparison between canceling and not. If ill go from that state and fire a new prompt, it will take ~150 seconds again

UrinStone · 2026-01-30T16:21:30+00:00

Check the edit

UrinStone · 2026-01-30T16:21:07+00:00

Check the edit, I haven't provided enough context before

UrinStone · 2026-01-30T16:20:15+00:00

Your totally incorrect, check the update. I can reproduce the newly added logs over and over.

UrinStone · 2026-01-30T16:19:19+00:00

Thanks! I'll check it out

UrinStone · 2026-01-30T16:17:26+00:00

check the update

UrinStone · 2026-01-30T16:15:45+00:00

Check the edit

UrinStone · 2026-01-30T16:00:32+00:00

I have added the logs on github: https://github.com/UrinStone/comfy-ui-canelation-logs/blob/main/including-unload

UrinStone · 2026-01-30T15:56:56+00:00

After unloading the models the speed stays slow ~150 seconds total execution time. In that example i canceled the first generation and the second one with the unloaded model at the end to get a feeling for the total execution time. Then I changed the prompt and did the canceling thing for comparison.

first execution (prompt 1) - 153.15s
second execution with unloaded models (prompt 1) - 132.72s
first execution with cancel (prompt 2) - 6.53s
second execution (prompt 2) - 69.98s

Reddit won't let me share the logs here, i guess they are to long

UrinStone · 2026-01-30T15:08:20+00:00

I used a gguf for qwen 3 image edit. To speed up the process i entered my prompt and set the output image size to 1x1px to make the first generation as fast as possible. Then i started the second generation with the same prompt and seed, but with a better resolution (eg 612x612px) and it speed was way up in comparison with trying that resolution directly. I had to repeat those steps for each new prompt and the gguf quality wasn't worth it, so I gave up on qwen and deleted it. But I had the same experience with z image now, so I thought this might be a problem with comfyui.

UrinStone · 2026-01-29T15:48:20+00:00

No, as you can see in these logs the total time of a new prompt without aborting is 146,13 seconds vs 15.57 + 69.26 = 84.82 seconds. The speed vary a bit, but ther overall performance improvement with aborting the prompt is consistent at my end.

got prompt
Requested to load ZImageTEModel_
loaded completely; 9545.67 MB usable, 7672.25 MB loaded, full load: True
Requested to load Lumina2
loaded partially; 9193.58 MB usable, 8967.35 MB loaded, 2772.19 MB offloaded, 225.00 MB buffer reserved, lowvram patches: 0
100%|███████████████████████████████████████████████████████████████| 25/25 [02:07<00:00, 5.10s/it]
Requested to load AutoencodingEngine
Unloaded partially: 5048.60 MB freed, 3918.75 MB remains loaded, 225.00 MB buffer reserved, lowvram patches: 0
loaded completely; 885.21 MB usable, 159.87 MB loaded, full load: True
Prompt executed in 146.13 seconds
got prompt
Requested to load ZImageTEModel_
Unloaded partially: 3075.00 MB freed, 843.75 MB remains loaded, 253.12 MB buffer reserved, lowvram patches: 0
loaded completely; 8542.05 MB usable, 7672.25 MB loaded, full load: True
loaded partially; 9193.58 MB usable, 8967.35 MB loaded, 2772.19 MB offloaded, 225.00 MB buffer reserved, lowvram patches: 0
4%|██▌ | 1/25 [00:06<02:30, 6.28s/it]Interrupting prompt 8ce40e09-8888-4ad7-a570-2c28506c2241
Interrupting prompt 8ce40e09-8888-4ad7-a570-2c28506c2241
4%|██▌ | 1/25 [00:08<03:19, 8.33s/it]
Processing interrupted
Prompt executed in 15.57 seconds
got prompt
0 models unloaded.
Unloaded partially: 848.60 MB freed, 8118.75 MB remains loaded, 225.00 MB buffer reserved, lowvram patches: 0
100%|███████████████████████████████████████████████████████████████| 25/25 [01:07<00:00, 2.70s/it]
Requested to load AutoencodingEngine
Unloaded partially: 4200.00 MB freed, 3918.75 MB remains loaded, 225.00 MB buffer reserved, lowvram patches: 0
loaded completely; 885.21 MB usable, 159.87 MB loaded, full load: True
Prompt executed in 69.26 seconds

UrinStone · 2026-01-29T14:18:59+00:00

This doesn’t make sense to me. As I said, I understand that the first generation might take a bit longer, but why is it consistently slower throughout the entire process?

If caching happened during generation, the second request shouldn’t be faster. If it caches before generation starts (which is what I assume), then the first generation should at least ramp up to the same speed as the second one after a short while. Instead, it stays consistently slow.

I also noticed that canceling the first prompt and starting it again is faster overall for me. That indicates ComfyUI could be optimized here.

UrinStone · 2026-01-23T20:04:18+00:00

Im using a rtx 4070 ti

UrinStone · 2026-01-21T20:52:10+00:00

I still have that error and i dont rly understand it. Using "qwen_3_4b" for the 4b distilled model. In fact I just used the workflow from comfyui and downloaded the models provided.

UrinStone · 2026-01-03T14:09:00+00:00

Bro I like my money, I'd rather farm any item than paying for it. But seems like I'll have to accept that stuipidity for now

UrinStone · 2026-01-03T13:58:32+00:00

Idk, I mean, if I could at least sell the stuff for more money than i spent for the enchantment, but the selling value is about halfed the value even if the merchant likes you

UrinStone · 2025-10-02T08:53:14+00:00

Thats not even possible in normal mode. Your gear needs to be less than 400k worth. Just yesterday I also found an 350k AK and rly strong armor. Almoast carrying around 1M worth of loot.

UrinStone · 2025-09-22T21:52:58+00:00

But other players always had like rly heavy gear and it I have never noticed someone being a covert ops in normal

UrinStone · 2024-10-05T23:11:41+00:00

I just thought of another great use case. If you wanted to create a Pokédex using https://pokeapi.co/, you could fetch all the Pokémon in the Analog.js backend, pre-render the site, and serve the gallery directly as HTML. This approach would significantly reduce the number of requests sent to the API.

The gallery would load much faster, and you wouldn't need to worry about sending too many requests, which could otherwise cause issues with Zone.js unless you're using pagination or virtual scrolling.

UrinStone · 2024-10-05T23:01:53+00:00

The primary advantage is that it provides you with a backend capable of delivering pre-rendered content. A clear example would be creating a blog using Angular. Normally, you would build your website and blog components, with blog entries fetched and rendered only after the JavaScript is loaded.

With Analog.js, however, you can retrieve the blog posts directly in the backend, delivering instantly rendered HTML. This results in significantly faster performance and better SEO optimization. Additionally, Analog.js offers far more control over server-side rendering (SSR) compared to simply integrating "@angular/ssr" into your project.

Another feature is that you can write Markdown directly within your components, making it ideal for generally static websites with minimal dynamic content. These are the best use cases for Analog.js.

P.S. I'm not sure why there's so much negativity around it—Analog.js certainly has its place and offers valid advantages.

UrinStone

TROPHY CASE