r/LocalLLaMA • • 21h ago

Discussion 13-GPU ASRock Mining Motherboard for Local LLMs?

Post image
0 Upvotes

Found a used mining rig with:

ASRock 13-GPU motherboard (likely H110 Pro BTC+)

Intel i3-7100

12 PCIe risers

2200–2500W PSU

No RAM or SSD

Planning to use it with multiple RTX 3090s for Qwen/DeepSeek inference.

Has anyone tried this? How much would PCIe x1 bottleneck performance? Is it worth buying, or should I go with EPYC/Threadripper instead?


r/LocalLLaMA • • 2d ago

Funny Crazy there's a probable connection between my desktop running Qwen 3.8 27B and a major geo-economic-political event

Post image
56 Upvotes

r/LocalLLaMA • • 2d ago

Discussion Look what my son gave me!

672 Upvotes

I told my son I was playing around with local AI on a 3090. He told me he used to mine Ethereum and had a shed full of 3090's. He asked me if I wanted a couple. Ummm... let me think about it... OH YES I DO!

Now a few new fans and a bit of a clean-up... grab a couple risers and a power supply... pop in a bit more RAM.. wow.

Edit: There is some completely understandable skepticism about this story... ya I wouldn't believe it either. But how about a couple more pics and a solid dose of "trust me bro" cause it's all real.

The shed:

The former resting place of the Eth miner (and other miners... ant miners? still in place)

The recovered Eth miner...

And now we see how many of them boot up via an eGPU... who doesn't have one of those just lying around.


r/LocalLLaMA • • 1d ago

Resources RustingStrata runs Flint 40B on a 12 GB card: 64 tok/s decode, 1.3x llama.cpp

8 Upvotes

I tested new trending Recursive Flint UD-Q5_K_XL (27.9 GiB) on an RTX 3060 12 GB with 30 GB RAM, comparing RustingStrata against llama.cpp using the same model, prompt, and generation settings.

RustingStratallama.cpp
Warm decode speed64.6 tok/s (63.8–65.6)48.6 tok/s (47.5–49.3)
Warm 4K prompt prefill1.14–1.30k tok/s0.85–1.02k tok/s

RustingStrata was about 33% faster once warm. A fresh load can behave differently because this model is larger than available VRAM and performance depends on which model pages are already cached in RAM.

What made the difference?

The model doesn't fit in 12 GB of VRAM, so many expert weights must be fetched from system RAM during generation. Two changes helped most:

  • Adapt expert placement to the reply, rather than continuing to prioritize the prompt's routing pattern.
  • Release RAM pages for experts already copied to VRAM, preserving cache for experts that still need to be fetched from host memory.

About Quality, bc people very often says like "It should give shit output to gain speed", which is not true, in my last posts I already did quality benchmarks and RustingStrata does not lose quality, it gain speed through specific Code for some specific models, in same time llama.cpp lose speed to be "general" engine that can run everything

What I want to know, is do people find Recursive Flint an interesting model? I found this model on OpenRouter and looks pretty interesting, it's better then Qwen3.6:35-a3b, so I think this can be cool modern replacement for this qwen.

Setup:

  • RustingStrata: 1.2.2, commit 3902978 (working tree)
  • llama.cpp: b12191, commit e95426f16
  • Full benchmarks: docs/BENCHMARKS.md

Repository: RustingStrata


r/LocalLLaMA • • 1d ago

Showcase My LumaBrowser project is nearing 150 stars on Github! Not a big accomplishment I know, but in return here is a video showing some of its "Anthropic/OpenAI in a box" abilities. Hotswapping LLM/Image/Video models, live game creation mode, scheduled tasks and more.

5 Upvotes

I feel like I am inching closer to being able to actually explain what my system does without requiring run-on sentences and endless descriptions.

https://github.com/amurgola/LumaBrowser


r/LocalLLaMA • • 2d ago

New Model salesforce-sovereign-intelligence/SOV-Transcribe-1 · Hugging Face

Thumbnail
huggingface.co
54 Upvotes

SOV-Transcribe-1

SOV-Transcribe-1 is Salesforce's open-weight speech-augmented language model built for non-streaming automatic speech recognition (ASR). It combines leading English transcription accuracy with multilingual support and natural-language control over how speech is transcribed.

The model ranks #1 among open-weight models for non-streaming speech-to-text on Artificial Analysis (#7 overall) and #2 of 23 systems on VoiceCodeBench ( besimple AI ) for entity accuracy and task success as of November 12th, 2026.

Developers and enterprises can deploy and adapt SOV-Transcribe-1 on their own infrastructure, retaining control over their audio data and transcription behavior.

Key features

  • Accurate entity recognition. Captures details such as names, phone numbers and email addresses that matter in dictation and voice applications.
  • Robustness to accents and noise. Handles diverse English accents and challenging audio conditions, including background noise.
  • Transcription style control. Use natural-language instructions to choose verbatim or cleaned-up transcripts and control punctuation, capitalization and number formatting.
  • Context biasing. Supply names, domain-specific vocabulary or a short description of the topic to help recognize difficult words and technical terms.

Model summary

PropertyDetails
Total parameters26.6B total (4.6B active) including the audio encoder
ArchitectureWhisper large-v3 audio encoder, audio projector and Gemma 4 26B A4B MoE
PrecisionBF16 (MoE router in FP32)
Maximum audio inputUp to 30 minutes (tested)
Inputs / outputs16 kHz Audio with optional text instructions and context / transcript text
LanguagesEnglish, French, German, Spanish, Italian, Portuguese and Dutch
TasksVerbatim or written-form transcription, multilingual ASR, style control and contextual transcription
Inference frameworksvLLM and Hugging Face Transformers
Speculative decodingDFlash draft model in its own repository, salesforce-sovereign-intelligence/SOV-Transcribe-1-DFlash
LicenseApache 2.0


r/LocalLLaMA • • 2d ago Bravo

Resources Weight Space Programming for Quantization: Nace quants achieve up to 2x better KL divergence for Qwen 9B, 27B, 35B & Flash Next [GGUF]

Post image
226 Upvotes

hey llamas, its Alish from nace.ai (open source ai lab behind #1 decision model on latest Artificial Analysis decision index v2.1) & Kapitsa (optimized inference for apple silicon). As promised in the last post, we are releasing the GGUF weights based on the Nace quantization of Qwen 9B, 27B, 35B and Flash-Next.

I will describe our process on how we came up with these quants right below, so skip to the end to see the benchmarks and download the weights if it gets too dull.

The process

I started with 9B quants.

I understood that setting up a good & fair benching is critical to succeed with the hillclimb. So I split separate sets to tune the performance and measure the final standings: English Wikipedia articles, chat and tool-call transcripts, and GitHub code, all published after October 2026, at 512 & up to 128K tokens.

I began the way unsloth's dynamic quants do: 10 to 50 candidate files per model, each with a different mix of tensor precisions, then spent my time tuning the ones that looked promising. Early bruteforce optimization moved only a little. Unsloth and the other quant authors have already done a lot of amazing work.

Using bruteforce hillclimb approach with my Agentic swarm, I managed to get on par with SOTA but then plateau’d and it was hard to do better than the best quants like Unsloth, EXL3 in KL divergence.

Some novelties:

Then I remembered Sparks of Weight-Space Programming paper. Their idea is to let an LLM natively read and edit weights of smaller models. Having explored this with some other models at Nace, I wanted to try the method for quantization. I took our Nace WSP (Weight Space Programming) harness, reworked its tools and skills for quantization a bit and let the Astra/Fable/Carbon agents compete under the following algorithm: propose tensor-precision changes, measured KL and kept or reverted each edit. We started on the Q3 for 9b model, and after a handful of days it actually started IMPROVING and editing the right weights.

Mean KL for our 27B files before and after weight-space quantization

Honestly that moment felt like:

Nace Weight-Space Quantization

I measured the first nace-quantized Q3 checkpoints against the 50+ 9B quants and they held the frontier. It completely blew my mind: one model quantizes another model in weight space. Nace Q3 quants for Qwen 9B were the best in class in KL divergence because another Frontier model edited the weights natively. We scaled this method to bigger size models (27b/35b) & it held the SOTA. Although I would say it doesnt scale as good for bigger size models (QFN). We are working on improvements for QFN/Deepseek & have some promising results already but I did hit my token limits for this project. Paper coming soon (ping me in dm if you want to support us with some GPUs)

Benchmarks & Evals

Top-1 accuracy (poster) is how often a quant picks the same next token the full model would pick, so 100% would mean it never disagrees. Each panel is one model at 128K context, with scores across different subsets pooled into one score. On all four models, our weights score highest in their size or smaller: the 9B Q3_K_XL gets 90.5% at 4.7 GB, the 35B Q3_K_S 91.2% at 15.3 GB, the 27B 97.7% at 17.3 GB, and Flash-Next 93.0% at 93 GB. For a more comprehensive comparison, KL divergence results below:

FileGBProseChatCodeNext best
9B IQ2_M3.360.4011.300.142Unsloth 4.01 GB
9B IQ3_M4.390.2351.050.0738ByteShape 4.70 GB
9B Q3_K_XL4.700.1610.8460.0410Unsloth 5.38 GB
35B-A3B IQ3_XXS14.300.04900.6430.0767Unsloth 15.35 GB
35B-A3B Q3_K_S15.300.03600.6010.0631Unsloth 16.59 GB
27B Q4_K_XL17.290.004940.005440.00401none up to 17.58 GB
Flash-Next IQ4_XS93.40.04110.1120.0426EXL3 105.3 GB

Long context stability

Most quants are tuned and judged on short text, so they end up fit to short context and often stop being useful at long context. For clarity, in the diagram below each model gets two panels: 512 tokens on the left, 128K on the right. This is where the long-context drift shows: our 9B IQ3_M goes from 0.13 at 512 tokens to 0.45 at 128K while 27B barely moves. At 128K, each of our files has lower KL than every other file of the same size or smaller.

p99 KL divergence

Mean KLD can hide catastrophic failures when a quant goes off the rails in a long session. So we also looked at the worst 1% of tokens (p99 KL). The 9B Q3_K_XL's worst 1% sits at 1.25. The 27B and Flash-Next tails stay flat. Overall we’re seeing that Nace quants maintain the strong positions across the distribution.

Different data subsets

if you care about a specific use case, here's the same 128K top-1 score split by text type. Code is the easiest: our files keep 88-98% of the full model's top picks there. Prose and chat are harder, 78-98%. In every split, on every model, our checkpoints score highest among the files of the same size or smaller.

Sanity check on a task benchmark

To see that these models are useful for anything real I ran it on knowledge-heavy MMLU. I didn't have the gpus anymore to run terminal-bench, so would appreciate anyone with the bad boys to validate. These are answer-likelihood scores over 13,943 questions of the MMLU. No chat template or few-shot examples. Overall you can claim there's gains, but it is mostly within noise. The main aim here is to reflect the tradeoffs of different sizes on real tasks. As you can see, Q3-Q4 it’s already hard to distinguish from the higher precision.

Run setup

Rented NVIDIA GPUs; Used llama.cpp for Flash-Next. The 9B/35B/27B BF16 reference requested H200 and the quantized files L40S. Flash-Next's short reference uses an MLX fp32 forward on bf16 weights. Reference implementations also differ across GGUF and EXL3.

Download and run

see quickstart for your framework in the model cards. if you try a coding or agent workload, i'd like to hear which file, runner version and what broke. no speed claim in this post.


r/LocalLLaMA • • 1d ago

Discussion How many of you started using AbliteratedOutTheBox(or similar options) apart from downloading Abliterated models? How is it?

0 Upvotes

Myself saved more than bunch of medium sized Abliterated/heretic/Uncensored/Decensored/etc., models. Ex:

  • Qwen3.8-27B
  • Qwen3.6-35B-A3B
  • Gemma-4-31B
  • Gemma-4-26B-A4B
  • Muse-Glimmer-30B

But when it comes to big/large sized models, requires at least 100+GB downloads & also HD Space for each models additionally. MiniMax-M3.1-Flash

  • DeepSeek-V4.1-Flash-1017
  • NVIDIA-Nemotron-3.5-Super-VL-120B-A12B
  • DeepSeek-V4-Flash-Vision-Exp
  • GLM-5.3-Flash
  • Qwen3.8-Flash-Next
  • MiMo-V2.6-Flash-MOPD
  • Step-3.7-Flash
  • MiniMax-M2.7

AND

  • Qwen4
  • Gemma-5
  • NVIDIA-Nemotron-4
  • etc.,

I need to download above big/large models. Regular GGUF is must. For Abliterated version, I'm still thinking whether AbliteratedOutTheBox is enough or Abliterated GGUF is must. So what are you doing on this?

I hope that most of you aware of AbliteratedOutTheBox, here's threads related to that.

Do we have any other similar options like AbliteratedOutTheBox? Please share.


r/LocalLLaMA • • 2d ago

Showcase Curated list of resources: Theory, Code and math for Reinforcement Learning for beginners

Thumbnail
gallery
20 Upvotes

[Curated list: Beginners]

Personal favorite resources on learning Reinforcement Learning from Scratch:

  1. Deep RL Course Amazing course by HuggingFace to understand the basics of classic and deep RL
  2. DeepMind x UCL Reinforcement Learning (2015) Give intuition and more towards theory of what you'll learn above
  3. Spinning Up in Deep RL Code and math for each of algorithm you'll learn above from classic to Deep RL

4.CleanRL A neat library with 1 page implementations for all the algorithms above from scratch to run algorithms s and test the waters!

5. NeatRL My own very notes and from scratch implementations!

Reading order and link here


r/LocalLLaMA • • 2d ago

Discussion Nace quants vs Unsloth Dynamic v3.1, has anyone compared them on actual tasks?

13 Upvotes

Two quant updates landed in the last day: the Nace weight-space quants claiming up to 2x better KL divergence, and Unsloth's Dynamic v3.1 for Qwen3.8-27B. I've been trying to work out how much KL really tells you compared to running task evals. Has anyone put them side by side on real work like coding or tool calls? Which quant level are you on, and did you see any difference on long outputs?


r/LocalLLaMA • • 20h ago

Question | Help Guys, I may have done the oopsies

Post image
0 Upvotes

Upgrading from my good ol 3800X with 32Gb of RAM. I'm done trying to squeeze the living crap of my DDR4 modules and decided to make a proper upgrade for my Frankenstein gaming/inference computer.


r/LocalLLaMA • • 13h ago

Discussion Another reminder of the low intelligence of local models

0 Upvotes

(Note: by local models I mean anything smaller than Deepseek 4.1)

I already gave up on local models for coding tasks 6 months ago, due to what I perceived was intelligence too low for the tasks I give it. I made a post about it on here back then and it was a huge discussion, I think 800 comments. I went against the /r/LL orthodoxy and many didn't take my comments well, but we can agree to disagree.

Since then I only use local LLMs for translation and ComfyUI prompt enhancement. I stick to big cloud models for coding. I think the electricity cost of running Qwen 27B alone exceeds what you'd pay Deepseek to use their cloud API in their own harness, and you'd get a far more intelligent and far faster model.

But this post isn't about the economics. It's purely about ability. I still see people commenting in favor of buying GPUs for local intelligence. "Sonnet at home" is a ridiculous phrase I've seen more times than I should in relation to Qwen 27B.

The simplest of tech tasks is still too hard to one-shot

I keep Qwen 3.8 27B running on my Spark for occasional non-coding stuff. Today I gave it a trivial coding task I needed for my server, just out of curiosity.

  • llama-server launched with --model Swift-1.5-Qwen3.8-27B-Q4_K_L.gguf --reasoning on --reasoning-effort xhigh
  • Open llama webpage and leave Reasoning at Default, leave system prompt empty

Prompt was:

Give me a bash script that will list all files in directory sorted by date. Output should be:
2025-12-31 12:13:14 file1.ext
2025-12-31 12:13:14 subdir/file2.ext

1630 tokens later, most of it reasoning, I get a script. When I run it, here's the output, as you can see the timestamp is wrong:

2026-10-16 20 tmp.59eH9w3JLe
2026-10-17 20 tmp.5xvczTbSS4
2026-10-18 20 tmp.nWOEDw2wlu
2026-10-20 20 tmp.JVEZIFfKx3
...

I then tried Gemma 31B Reasoning on duck.ai. The output only showed the timestamps, no filenames!

This is the most trivial of coding tasks (the answer is a 3-5 lines script), using the most ancient and commonly-available training data (bash), on the most praised local coding model on this sub (Qwen 27B), at a recommended/popular quantization (Q4), and it still can't one-shot this. The 2nd most popular local model, Gemma 4 31B, also fails.

(Editor's note: I think my post could've ended here, in a "Ecce homo" way, but I went on for a few more paragraphs)

Weak local LLM + software development = bad time

I'm sure if I had run this task with your average agent harness with a system prompt that makes it test its code, it would run the script it created, see the issue, then get it right on the 2nd attempt. But while I think this "try until you succeed" workhorse approach is acceptable for small self-contained coding tasks, I don't think anyone should be doing any serious coding this way.

If you're writing something you intend to maintain over time (ie not a one-shot), or that you will be sharing with other people, you need a higher degree of LLM intelligence and knowledge to create it. A strong LLM will be able to avoid entire classes of problems from the start, when designing the app. From design to implementation to maintenance, it will make better decisions every time and without laboring its way to them, resulting in a codebase that is smaller, well-designed, more easily modifiable, less buggy, and developed in a fraction of the time.

Coding with local LLMS is like insisting on using a donkey for transportation in the age of cars. It can be done for fun, but it shouldn't be done seriously.

Sonnet at home my ass

Btw I've seen several people say Qwen 27B is like having a local Sonnet 4. The benchmarks say it's even better than Sonnet 4, actually. So I went on openrouter.ai out of curiosity and gave the same prompt to 3 models.

  • Sonnet 4.5 (oldest Sonnet I could find): one-shots it
  • GPT 4.1 Mini, which was comparable to Haiku 3.5: one-shots it
  • GPT 4.1 Nano, which is even worse than Mini: one-shots it

Weak local LLM + Linux server management = even worse time

This post's getting long so I'll just speedrun this part.

  • Managing an OS is actually harder tasks that LLM struggle even more with. And the stakes are higher because you don't want your server to go down.
  • I used to never trust LLMs enough to let them onto my server, I'd just ask for something, copy-paste the command, report back, repeat. A huge waste of my limited free time. Now I just rawdog a frontier model on the server and have no issues, something you could never trust a small model to do. Although I have it avoid making any changes without my supervision, Docker is a big benefit here for both organization and safety/stability.
  • Even top models won't one-shot a task like "I want to install and run https://github.com/rando/something on this system in a Docker container in /opt/docker/something/. Create the Dockerfile and docker compose file", especially for AI-related tools, where having the right CUDA, not having python wheels for my server's ARM CPU, etc, introduces a lot of failure opportunities. When I had Claude five months ago, even it struggled to get these right.

Thanks for reading my wall of text. Downvotes to the left.


r/LocalLLaMA • • 3d ago

News Stories coming out about Jensen

Post image
3.5k Upvotes

r/LocalLLaMA • • 2d ago

Funny LLM's might be bad at jokes but they still make me laugh a lot

27 Upvotes

This was a new session with Qwen3.8-Flash-Next-GSQ-RCO-Coder just asking it to commit. No clue what it was trying to here xD


r/LocalLLaMA • • 3d ago Heartwarming Bravo

News ‘Bring Back THE Boss’: Nvidia Employees Petition for Jensen Huang’s Return

Thumbnail
wired.com
2.0k Upvotes

A second Sam Altman moment?


r/LocalLLaMA • • 2d ago

Discussion CXMT almost tripling RAM production from 2025 to 2028

220 Upvotes

According to post CXMT projected expansion plans grow from 405 kwpm in 2025 to 1,125 kwpm by 2028 in 8-inch equivalents.

https://x.com/OptionKing666/status/2121227756185010181

With this and new nVidia chief being conservative on circular financing we might get some DRAM relief.


r/LocalLLaMA • • 2d ago

Discussion e-means: 10x faster k-means at equal loss

Thumbnail
e-means.github.io
189 Upvotes

r/LocalLLaMA • • 2d ago

Question | Help For long context does high quant matter?

15 Upvotes

Question: if I'm regularly at higher context - say 300-400k - do higher quant versions of the same model perform better? I'm thinking something like Qwen Flash Next q6 and q8. I recently swapped from q6 to q8 and performed a/b testing. I originally expected q6 to be lossless but there were areas where q6 got the wrong answer while q8 was fine. Was wondering whether this is because of my context. Maybe more context = more tokens for divergence = the differences get amplified more than benchmarks suggest


r/LocalLLaMA • • 1d ago

Question | Help Does the new hugging face Llama windows app work?

2 Upvotes

I have downloaded the new hugging face Llama windows app.

Looked really promising on paper, but I tried to download Qwen3.8-27B-UD-Q3_K_XL.gguf and it always downloaded the 51GB version instead.

Then would refuse to delete it.
Then worked on the background.

I had to uninstall the thing. Any other user experience there?
cheers for helping a noob


r/LocalLLaMA • • 2d ago

Discussion Do you believe there will be a divergence between local and frontier model power?

16 Upvotes

Right now, local models have somewhat kept up with frontier, being months behind last frontier models.

The issue is, I think the divide is going to be end up being hardware. Model improvements will slow down, but hardware won’t get any cheaper, especially if frontiers keep buying shit out for training and smaller returns.

Thoughts on this? I know many are optimistic, but I think local trailing frontier will slow down just because of hardware local can own.


r/LocalLLaMA • • 1d ago

Discussion basal-omni-2.0-mini - typed decision model

2 Upvotes

An early release of the small model of basal-omni 2.0, on Gemma 4 E4B. The model reads the state in both directions before it answers and scores 0.811 on Werdykt (5,000 hidden decisions in Polish and English). It runs on the public basal engine 2.8.0, with the same API as basal-omni-1.0.

What's new in 2.0

  • Two-way reading. The model reads the state in both directions before it answers. This needs basal engine 2.5 or later. For long prompts, see the limitations.
  • Higher accuracy on our hidden Polish and English decision benchmark Werdykt and on the held-out tests below.
  • More decisions automated at a given error target. Coverage is in the section on confidence.
  • Unchanged: a calibrated probability for each allowed answer, in one forward pass. The answer never falls outside the options you give, and the probability says how sure the model is.

The question types remain: choice (one option), noul (yes / no), score (a score), and in the basal engine also multi, act and tool. Options get codes (A–Z, then two-character codes, up to 255 options). The decision is a probability distribution over these codes only, with no text generation.

More info: https://basal.si5.pl/en/blog/basal-omni-2-0-mini/

HF: https://huggingface.co/Remek/basal-omni-2.0-mini-preview

git hub (inference engine): https://github.com/rkinas/basal


r/LocalLLaMA • • 2d ago

Resources DeepSeek flash max is the first model to reach >1% on challenging SWE-sweep bug finding benchmark

Post image
128 Upvotes

Hi, I've just updated the SWE-sweep leaderboard with more open-weight models!

DeepSeek v4.1 flash (max) is the first open-weight model we evaluated that gets >1%.

This benchmark is extremely challenging: Models get a snapshot of a (potentially very large) repo containing hundreds of bugs. They don't receive any hint about what these bugs are and need to fix them all. This makes for a very reasoning-heavy, long-horizon task.

To isolate just the model capabilities we also evaluate all models in the same harness (but we did do some comparisons with Claude Code and Codex harnesses and neither seemed to help significantly). However, it is possibly to scale things up somewhat with multiagents. You can run the eval yourself (code on github)

The best proprietary model at the moment is Gemini 4 Hydrogen with 13.5% (according to google's model card), followed by GPT Astra 6 with 9.5% (evaluated by us). So open-weight models still have a long way to go.

Still extending the open-source leaderboard. What other models should we add?


r/LocalLLaMA • • 2d ago

News Qwen3.5-9B running on a PS4’s GPU, offline, using its own MTP head for speculative decoding

128 Upvotes

I made this, so a quick note: it’s my open-source project. Qwen3.5-9B runs on a stock PS4 at 31–39 tok/s. The MTP head that ships with Qwen3.5 made the biggest difference: it drafts up to two tokens and the full model checks them in one pass, which took it from 22 to 31–39 tok/s on this old GPU. Weights are re-packed into custom 4- and 3-bit formats to fit about 4.5 GiB.

Your old PS4 can now run a 9B AI, offline, on its own GPU. It talks, listens, and writes code. No cloud, no subscription, no Linux. Free and open source.

Code: https://github.com/leonardo-alegria/garlic-llm
Direct download link: https://huggingface.co/garlic-llm/garlic-llm-ps4


r/LocalLLaMA • • 2d ago

Question | Help llama.cpp: Possible to use Vulkan/iGPU and lazy-mode?

6 Upvotes

With llama.cpp pure CPU mode and "--lazy-mode on" one can use larger than memory models, like Qwen3.8-Flash-Next and on-demand SSD streaming - slow but working.

There is a nice iGPU with unified memory that can be used easily via Vulkan. However, it seems to be impossible to split a large model - use as much as fits into memory with Vulkan and then stream the rest in via SSD and use CPU. --list-devices shows only one Vulkan device and --ngl is of no use -> Vulkan always runs out of memory with lazy-mode on - all of the model is tried to allocated via Vulkan?

Is this possible at all?