Orakul Studio - Zero-Disk VRAM Streaming Engine
Important Note on RAM/VRAM & Internet Requirements
- Identical Memory Footprint: Memory consumption (System RAM & VRAM) is 100% identical whether you load a model locally or stream it via Zero-Disk.
- Zero Disk Consumption: You save 0 bytes to your local drive. No temp files, no local caches, and zero SSD/HDD write cycles or wear.
- Saves Slow Drives: If you are using a traditional HDD or have a full SSD, streaming over a fast connection completely bypasses local disk bottlenecks.
- Speed is Key: The only requirement is a fast and stable internet connection. If your system can already run Flux 2, you can stream models and LoRAs of any size (even 50GBβ100GB+) seamlessly without freeing up a single gigabyte of storage!
Viking HF Multi-LoRA Loader (Zero-Disk VRAM/RAM Streaming Engine)
An official, free companion API node for my experimental and high-rank models hosted on Civitai.
Many of my experimental LoRA models are 20β40 GB in size. If you have a fast internet connection but donβt want to fill up terabytes of your SSD space just for testing, this node is your solution. It allows you to stream large model weights directly from my Hugging Face archive into your PCβs RAM/VRAM, completely bypassing the need to save files to your local disk.
Key Advantages
- Zero-Disk Architecture: Models are downloaded directly into RAM. You can test dozens of massive LoRA models without them occupying a single megabyte of space on your storage drive.
- Identical RAM Usage: The node consumes exactly the same amount of RAM as it would if you were loading a model already saved on your local disk. No extra resources are wasted.
- Smart RAM Cache: With the
keep_in_ramtoggle, you control the model's lifecycle: - ON: The model is loaded into RAM once and remains there, allowing for near-instant subsequent generations.
- OFF: The model is downloaded, used to generate an image, and then immediately cleared from memory, freeing up system resources entirely.
- 4 Slots for Multi-Generation: The node features 4 independent slots, each with its own strength settings (
str_model,str_clip). You can blend different models on the flyβfor example, by combining a character-specific LoRA with a style-based LoRA (such as one for tattoos) in a single generation. ---
How It Works (For Users of My Models)
The node is hardcoded to point to my repository (OrakulStorm/Zero-Disk-VRAM-Streaming-Engine). This ensures everything stays configured correctly, sparing you from having to enter redundant information. The interface follows a simple "copy-paste" workflow.
Steps to follow:
- Go to my Hugging Face repository and open the Files and versions tab.
- Copy the path to the desired
.safetensorsfile.
- Example of a copied path:
FLUX2-RANK2048-VanGogh/r2048f2dvangog.safetensors
- Paste this path into the
filename_1field (or any available slot in the node). - Ensure the
lora_1_switchtoggle is set to ON. - Click Queue Prompt β thatβs it! The node will automatically fetch the required model from my repository directly into memory and generate the result.
(You do not need to change the repo_id field in the ComfyUI interface; it serves merely as a visual indicator of which repository is being accessed.)
π¨βπ» For Advanced Users (Using Other Repositories)
The nodeβs code is fully open-source. If you are familiar with Python and would like to use this "Zero-Disk" streaming engine with other models (such as official Flux weights, Diffusers, etc.), you can easily detach the node from my repository. How ββto change the base repository:
- Open the
__init__.pyfile (located in thecustom_nodes/VikingHFnode folder) using any text editor (e.g., Notepad++). - Locate the
class VikingHFMultiLoraLoader:definition and scroll down to thedef INPUT_TYPES(s):block. - Within the slot settings, find the following line:
"repo_id_1": ("STRING", {"default": "OrakulStorm/Zero-Disk-VRAM-Streaming-Engine"}), - Replace
"OrakulStorm/Zero-Disk-VRAM-Streaming-Engine"with the ID of your desired Hugging Face repository. - Save the file and restart ComfyUI.
You can now provide paths to .safetensors files from your target repository. If the repository is private, remember to enter your access token into the hf_token field within the node's interface.
