DGX Monarch - Dual Spark Rendering w/ ComfyUI

For those of you who have been wanting to utilize your dual Spark cluster for image/video gen with ComfyUI - today is your day.

I started this personal project back in April of this year, and it’s at a point where I’m fine with a public release.

To put this as simply as possible - you can get nearly 2× render speeds with this repo. Results vary by model and settings. BF16/FP8/NVFP4/INT8/etc. supported, depending on the model. No GGUF.

Link to the repo: https://github.com/Deen-Media/dgx-monarch (highly recommend reading the FAQ after the README)

The rest of this will be MUCH more boring, so you can skip if you just want to start using it. You’ve been warned, and I cannot refund any time spent reading what you already have thus far, and especially the rest of this post. More words. Four more pointless words. K just checking.

Before you ask - yes, I heavily used AI to develop this. But most of MY time was spent validating outputs and performance, and actually using this project.

In terms of maintainability, well, I have and will continue to do my best to keep the development workflows I’ve built up to date so that new models can be safely added without breaking anything. I do not intend on sharing these development workflows, as I personally do not see the value in doing so relative to the effort I would need to put into making sure they are even safe for me to share. To be clear, I mean my personal AI-agent development workflows, not the example ComfyUI workflows included in the repo. Workflows like this, in my opinion, should be something you craft and tailor/customize yourself.

I’m fully expecting AI-generated PRs, and I realize at the end of the day it’s my slop vs. yours. All I ask is that you actually sit down and validate/render/test your changes and include those results. I’ll need time to review and test them too, so please be patient. I really enjoy USING this tool and would like to continue to do so. Maintaining comes second to me personally, but ironically, using and maintaining go hand in hand.

It’s easy to vibe-code a small project. It is VERY difficult and costly (money, not just time) to vibe-maintain a large project.

For transparency, a project like this has depleted (and I mean 0%/flatline), on a weekly basis, the following subscriptions of mine since the start:

OpenAI:

\- 1× Astra $200 account\* (now Astra $500 account\*\*)

\- 1× Business Astra seat

\*I took advantage of every single banked/global reset and got real lucky on the global ones.

\*\*Strictly to close extra sloppy PRs hella fast with ultrafast (but really to utilize usage on spontaneous global resets that the community gets an hour or two heads up on). Plus I enjoy paying more than double to have roughly the same usage as I had before.

Anthropic:

\- 1× Fable $200 account

\- 1× Business Fable seat

Cursor:

\- 1× Fable $200 account (Grok did not touch the working code - it had a different use case)

Google:

\- 1× Ultra $250 account (don’t freak out - Gemini did not touch the working code)

(Note: Astra/Fable were not around when this project started. Was fun.)

I will maintain these subscriptions for as long as reasonably possible, as I do have other projects I intend on releasing (more DGX-specific ones) in the coming months here.

However, there WILL be a point where it won’t make sense to maintain all these subscriptions. Whether that’s due to local models finally being sufficient/effective enough to handle my workflows, frontier costs skyrocketing or usage allowances dwindling as the era of subsidization ends, or the projects simply no longer needing a high level of maintenance (unlikely).

That’s all, thanks for reading.