Radiata VS automatic

I didn't and don't! Are you saying that can be applied in the a1111 gui? The things I've found by googling it seem to be about a separate UI which uses this optimisation to radically speed up generation.

wow You might be into something here I am going to try this today. Have you tried Lsmith is MIA for 1 month now but is base on TensorRT and it was supper fast when I ran it you need to convert the models to tensorRT format but once they run they are blazingly fast https://github.com/ddPn08/Lsmith

If you just want an accelerated ui, you can check https://github.com/ddPn08/Lsmith/ or https://github.com/VoltaML/voltaML-fast-stable-diffusion which also use the same origina nvidia code. These projects don't do img2img though, you can check in my repo for the img2img pipeline if you need. You need to compile the tensorrt engines for the models first. There are a few steps you can check in their script: export onnx, optimize onnx, compile engine for optimized onnx. I streamlined that a bit and I normally just run my compile.py in docker to build engines.

I just found this amazing GUI that uses the accelerated models of SD to get a speed boost of up to 30%. https://github.com/ddPn08/Lsmith

just released https://github.com/ddPn08/Lsmith

> it won't ever be a viable option

For production workloads, I generally agree. It's an unsupported hack with a questionable future, I wouldn't do anything money-making with it.

However, for tinkering and consumer workloads, it already works pretty well. Enough of cuDNN and cuBLAS work to run PyTorch and in turn, Stable Diffusion with https://github.com/lshqqytiger/ZLUDA - there's even a fairly user-friendly setup process already in https://github.com/vladmandic/automatic .

I was able to get a personal non-ML related project working on my AMD card in just a few minutes, which saved me a lot of development time before I then deployed the production workload on NV hardware (this is probably why AMD pulled the plug on the project - it's almost more of a boost to NV than anything else, AMD really need people to be writing code on ROCm to deploy on AMD datacenter hardware).

While I currently use SD.Next[1], I have tested ComfyUI locally with my AMD card. The UI can be daunting, but you learn quite a great deal about how a Stable Diffusion pipeline works. In addition some innovations and advances find their way into ComfyUI first.

[1] https://github.com/vladmandic/automatic

I used SD.NEXT ( https://github.com/vladmandic/automatic ) and https://civitai.com/models/82098/add-more-details-detail-enhancer-tweaker-lora and epicphotogasm_lastUnicorn

I found this thread on GitHub talking about how this was fixed in the latest version with an optional setting. I tried enabling it, as they mentioned, but it just resulted in an immediate CUDA out of memory error when starting generation. So it seems I'm actually needing the shared memory, which I assume is my issue.

As always, do check out our more detailed changelog, give us a quick install from our Repo, and stop by our Discord Server for any questions or help you may need.

SD.Next

Today I finally wanted to give SDXL a chance, so I set everythin up according to Vladmandic's Wiki https://github.com/vladmandic/automatic/wiki/SD-XL

I'm trying to get SDXL working on Vlad's SDNext, but I keep getting the error in the title when trying to run basic operations. I'm not sure what's going on, I followed his guide for it to a T.

We used an inference container based on SDNext, along with a custom worker written in Typescript that implemented the job processing pipeline. The worker used HTTP to communicate with both the SDNext container and with our batch framework.