<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Orkun Soylu</title><link>https://orkun.soylu.me/</link><description>Notes from my homelab: open-weight LLMs tested on my own GPUs, plus writing on AI, technology and running IT. What actually works, with the numbers.</description><language>en</language><atom:link href="https://orkun.soylu.me/rss.xml" rel="self" type="application/rss+xml"/><item><title>Strata @W7800 + RX 7900 XTX</title><link>https://orkun.soylu.me/posts/2026-10-10-strata-dual-gpu/</link><guid>https://orkun.soylu.me/posts/2026-10-10-strata-dual-gpu/</guid><pubDate>Sat, 10 Oct 2026 00:00:00 GMT</pubDate><description>I split Qwen3.8-Flash-Next by layer across 72 GB of VRAM and system RAM dropped out of the picture entirely. Decode barely moved (72 → 74 tok/s); long-prompt prefill gained 24% (961 → 1,190 tok/s) — less than I expected, because each card needs its own prompt buffers.</description><category>strata</category><category>multi-gpu</category><category>moe</category><category>amd</category></item><item><title>Strata 125B MoE @48 GB vs Qwen3.8-27B</title><link>https://orkun.soylu.me/posts/2026-10-09-strata/</link><guid>https://orkun.soylu.me/posts/2026-10-09-strata/</guid><pubDate>Fri, 09 Oct 2026 00:00:00 GMT</pubDate><description>A purpose-built engine runs a 125B mixture-of-experts on my single W7800 by keeping the hot experts in VRAM and the rest in RAM. Tuned, the 3-bit build matches or beats my 27B baseline on quality and is 40–60% faster per token — but tool-heavy answers arrive 38% later.</description><category>strata</category><category>moe</category><category>rocm</category></item><item><title>Coder390 EfficientThink vs Qwen3.8-27B</title><link>https://orkun.soylu.me/posts/2026-10-09-coder390/</link><guid>https://orkun.soylu.me/posts/2026-10-09-coder390/</guid><pubDate>Fri, 09 Oct 2026 00:00:00 GMT</pubDate><description>A community fine-tune that promises to cure over-long thinking tied the official Qwen3.8-27B on quality in all three of my tests, and was 4–5% slower per token. The long tail it's built to fix never showed up in my workloads.</description><category>coding</category><category>fine-tunes</category><category>qwen</category></item><item><title>DavidAU TURBO &amp; Swift vs Qwen3.8-27B: thinking tokens</title><link>https://orkun.soylu.me/posts/2026-09-23-thinking-token-claims/</link><guid>https://orkun.soylu.me/posts/2026-09-23-thinking-token-claims/</guid><pubDate>Wed, 23 Sep 2026 00:00:00 GMT</pubDate><description>Two fine-tunes that promise far fewer thinking tokens didn't deliver: TURBO thinks the most of all three (58% of its output), and Swift's claimed 58% reduction came out at 15%. One run per prompt would have told me the opposite story.</description><category>reasoning</category><category>fine-tunes</category></item><item><title>llama.cpp ROCm vs Vulkan @W7800</title><link>https://orkun.soylu.me/posts/2026-09-23-llamacpp-rocm-vs-vulkan/</link><guid>https://orkun.soylu.me/posts/2026-09-23-llamacpp-rocm-vs-vulkan/</guid><pubDate>Wed, 23 Sep 2026 00:00:00 GMT</pubDate><description>Current llama.cpp is only 3% faster than the runtime bundled with Ollama. Vulkan (RADV) decodes 4.6% faster than ROCm but prefills 16% slower. And the card is capped at 230 W, with no way to raise it.</description><category>llama.cpp</category><category>rocm</category><category>vulkan</category><category>amd</category></item><item><title>W7800: bare metal vs Proxmox VM</title><link>https://orkun.soylu.me/posts/2026-09-23-bare-metal-vs-vm/</link><guid>https://orkun.soylu.me/posts/2026-09-23-bare-metal-vs-vm/</guid><pubDate>Wed, 23 Sep 2026 00:00:00 GMT</pubDate><description>Moving my W7800 from a bare-metal box into a Proxmox VM on another host changed generation by 2% (noise) and made prompt processing 8% faster. Passthrough itself costs nothing measurable — but I had to get past four setup traps first.</description><category>virtualization</category><category>amd</category><category>performance</category></item><item><title>Own Q6_K (Turkish imatrix) vs Q8_0 vs ISTA IQ3_S</title><link>https://orkun.soylu.me/posts/2026-09-22-own-quantization-q6k/</link><guid>https://orkun.soylu.me/posts/2026-09-22-own-quantization-q6k/</guid><pubDate>Tue, 22 Sep 2026 00:00:00 GMT</pubDate><description>I made a Q6_K with a 145K-token calibration set (40% Turkish), and it stays 10× closer to Q8_0 than ISTA's 3-bit does (KLD 0.0056 vs 0.056). My targeted imatrix beat a bigger generic one by 4–7%. But with MTP on, Q6_K is slower than Q8_0.</description><category>quantization</category><category>llama.cpp</category></item><item><title>MTP speculative decoding @Ollama: 20 → 42 tok/s</title><link>https://orkun.soylu.me/posts/2026-09-22-mtp-speculative-decoding/</link><guid>https://orkun.soylu.me/posts/2026-09-22-mtp-speculative-decoding/</guid><pubDate>Tue, 22 Sep 2026 00:00:00 GMT</pubDate><description>Turning on the model's built-in multi-token-prediction head more than doubled generation speed without changing quality. Four draft tokens is the sweet spot, and the gain depends a lot on content — code accepts drafts far more often than Turkish prose.</description><category>speculative-decoding</category><category>ollama</category><category>performance</category></item><item><title>empero 35B-A3B vs Qwen3.8-27B Q8+MTP vs ISTA IQ3_S @CVE triage</title><link>https://orkun.soylu.me/posts/2026-09-22-cve-empero-q8-ista/</link><guid>https://orkun.soylu.me/posts/2026-09-22-cve-empero-q8-ista/</guid><pubDate>Tue, 22 Sep 2026 00:00:00 GMT</pubDate><description>A distilled 35B-A3B MoE answers 2.4× faster but drops to 0.84, with unsafe upgrade advice and a hallucinated CVE. On my W7800, Q8_0+MTP ties ISTA IQ3_S at 0.96 while answering 1.7× faster.</description><category>security</category><category>moe</category><category>fine-tunes</category></item><item><title>vLLM vs Ollama @W7800 (ROCm)</title><link>https://orkun.soylu.me/posts/2026-09-21-vllm-rocm-w7800/</link><guid>https://orkun.soylu.me/posts/2026-09-21-vllm-rocm-w7800/</guid><pubDate>Mon, 21 Sep 2026 00:00:00 GMT</pubDate><description>Of the seven quantization formats I tried, two ran on RDNA3 under vLLM 0.27. int8 W8A16 + MTP reached 42 tok/s; int4 W4A16 reached 57 tok/s but locked up the GPU at ~30K tokens. I removed vLLM — and Ollama with MTP matched it the next day.</description><category>vllm</category><category>rocm</category><category>amd</category></item><item><title>ornith-1.5 35B MoE @CVE triage</title><link>https://orkun.soylu.me/posts/2026-09-18-ornith-cve/</link><guid>https://orkun.soylu.me/posts/2026-09-18-ornith-cve/</guid><pubDate>Fri, 18 Sep 2026 00:00:00 GMT</pubDate><description>A 35B mixture-of-experts with only 1.9B active parameters decodes at 84 tok/s and answers in 39 s — but its score drops to 0.83, with consistently unsafe upgrade advice. My CVE prompt actually made it slightly worse.</description><category>security</category><category>moe</category><category>fine-tunes</category></item><item><title>ISTA IQ3_S: general capability</title><link>https://orkun.soylu.me/posts/2026-09-17-ista-general-capability/</link><guid>https://orkun.soylu.me/posts/2026-09-17-ista-general-capability/</guid><pubDate>Thu, 17 Sep 2026 00:00:00 GMT</pubDate><description>On my 16 GB card, ISTA's 3-bit Qwen3.8-27B nearly maxes out everyday benchmarks: 40/41 HumanEval, 49/50 GSM8K, 9/9 long-context recall, 15/15 tool calls. The one weakness I could see is Turkish reading comprehension (36/40 vs 40/40 in English).</description><category>quantization</category><category>qwen</category><category>nvidia</category></item><item><title>HauhauCS Aggressive Q8 vs 3-bit @CVE triage</title><link>https://orkun.soylu.me/posts/2026-09-17-hauhau-q8-cve/</link><guid>https://orkun.soylu.me/posts/2026-09-17-hauhau-q8-cve/</guid><pubDate>Thu, 17 Sep 2026 00:00:00 GMT</pubDate><description>Running the same fine-tune at Q8 on my 48 GB W7800 lifts its CVE score from 0.92 to 0.97 — most of its weakness was the 3-bit compression. But it still doesn't beat ISTA's 3-bit, and it costs 2.4× the time and 2.5× the energy per token.</description><category>security</category><category>quantization</category><category>fine-tunes</category></item><item><title>CVE system prompt v2: ISTA IQ3_S @0.98</title><link>https://orkun.soylu.me/posts/2026-09-17-cve-prompt-v2/</link><guid>https://orkun.soylu.me/posts/2026-09-17-cve-prompt-v2/</guid><pubDate>Thu, 17 Sep 2026 00:00:00 GMT</pubDate><description>A stricter grounding rule plus two tool fixes took ISTA to 0.98, with zero CVEs from memory and zero language drift. HauhauCS slipped to 0.92: it gives up researching upgrades too early.</description><category>security</category><category>prompting</category><category>tool-use</category></item><item><title>CVE system prompt v1</title><link>https://orkun.soylu.me/posts/2026-09-17-cve-prompt-v1/</link><guid>https://orkun.soylu.me/posts/2026-09-17-cve-prompt-v1/</guid><pubDate>Wed, 16 Sep 2026 00:00:00 GMT</pubDate><description>One shared system prompt took HauhauCS's English answers from 15 down to 1 and improved fix-version accuracy for both models. The facts from memory stayed — now labelled 'unverified', but still wrong.</description><category>security</category><category>prompting</category><category>tool-use</category></item><item><title>ISTA IQ3_S vs Unsloth UD-IQ3_S @16 GB</title><link>https://orkun.soylu.me/posts/2026-09-16-ista-vs-unsloth-iq3/</link><guid>https://orkun.soylu.me/posts/2026-09-16-ista-vs-unsloth-iq3/</guid><pubDate>Wed, 16 Sep 2026 00:00:00 GMT</pubDate><description>On my RTX 4070 Ti SUPER under vLLM, ISTA's IQ3_S gets 1.2% lower perplexity from a smaller file and prefills 8% faster; Unsloth's decodes 5% faster and leaves a bit more room for KV.</description><category>quantization</category><category>vllm</category><category>nvidia</category></item><item><title>ISTA IQ3_S vs HauhauCS IQ3_XS @16 GB: features</title><link>https://orkun.soylu.me/posts/2026-09-16-ista-vs-hauhau-features/</link><guid>https://orkun.soylu.me/posts/2026-09-16-ista-vs-hauhau-features/</guid><pubDate>Wed, 16 Sep 2026 00:00:00 GMT</pubDate><description>Both 3-bit Qwen3.8-27B builds pass vision, tool calling (with and without thinking), using tool results and thinking control on my RTX 4070 Ti SUPER, at ~43–44 tok/s with 64K fully on the GPU.</description><category>tool-use</category><category>vision</category><category>fine-tunes</category></item><item><title>ISTA IQ3_S vs HauhauCS IQ3_XS @CVE triage</title><link>https://orkun.soylu.me/posts/2026-09-16-cve-baseline/</link><guid>https://orkun.soylu.me/posts/2026-09-16-cve-baseline/</guid><pubDate>Wed, 16 Sep 2026 00:00:00 GMT</pubDate><description>The first run of my tool-using CVE evaluation: both 3-bit 27B models scored 0.96. What separated them wasn't accuracy but language discipline — HauhauCS answered a third of my Turkish questions in English.</description><category>security</category><category>tool-use</category><category>nvidia</category></item><item><title>vLLM vs Ollama @RTX 4070 Ti SUPER</title><link>https://orkun.soylu.me/posts/2026-09-16-vllm-vs-ollama-power/</link><guid>https://orkun.soylu.me/posts/2026-09-16-vllm-vs-ollama-power/</guid><pubDate>Tue, 15 Sep 2026 00:00:00 GMT</pubDate><description>For a single user, Ollama beat vLLM on every axis I measured: 28% faster decode, 1.9× faster prefill, 2.5× the context in VRAM, a 3-second start and less energy per token.</description><category>vllm</category><category>ollama</category><category>power</category><category>nvidia</category></item><item><title>Qwen3.8-27B: thinking on vs off</title><link>https://orkun.soylu.me/posts/2026-08-19-thinking-on-off/</link><guid>https://orkun.soylu.me/posts/2026-08-19-thinking-on-off/</guid><pubDate>Wed, 19 Aug 2026 00:00:00 GMT</pubDate><description>With think=false the model just moves its reasoning into the visible answer, which gets longer. It only wins on plain fact lookups; on questions that need reasoning, thinking mode was 22–40% faster.</description><category>reasoning</category><category>qwen</category></item><item><title>pi harness: Qwen3.8-27B Q4_K_M vs Q8_0</title><link>https://orkun.soylu.me/posts/2026-08-19-pi-agent-27b/</link><guid>https://orkun.soylu.me/posts/2026-08-19-pi-agent-27b/</guid><pubDate>Wed, 19 Aug 2026 00:00:00 GMT</pubDate><description>All 13 of my agent runs fixed the bug or built the feature, with zero failed exact-match edits. Q8_0 was up to 78% slower and no more accurate. Almost all the waiting went into re-reading the prompt.</description><category>agents</category><category>coding</category><category>qwen</category></item><item><title>Dense 27B @168k token prompt</title><link>https://orkun.soylu.me/posts/2026-08-19-168k-context/</link><guid>https://orkun.soylu.me/posts/2026-08-19-168k-context/</guid><pubDate>Wed, 19 Aug 2026 00:00:00 GMT</pubDate><description>I fed a 168,084-token prompt to Qwen3.8-27B Q8_0 on my W7800: prefill took 11.7 minutes, and generation fell from 20.2 to 9.6 tok/s. It still recalled a marker from the very start perfectly.</description><category>long-context</category><category>vram</category><category>ollama</category></item><item><title>W7800 vs RX 7900 XTX</title><link>https://orkun.soylu.me/posts/2026-08-18-w7800-vs-7900xtx/</link><guid>https://orkun.soylu.me/posts/2026-08-18-w7800-vs-7900xtx/</guid><pubDate>Tue, 18 Aug 2026 00:00:00 GMT</pubDate><description>I ran the identical Q4_K_M blob and Ollama version on both cards: the consumer 7900 XTX is 29% faster at generation and 44% faster at prefill. The gap follows compute, not bandwidth — what the W7800 really offers is its 48 GB.</description><category>gpu</category><category>amd</category><category>rocm</category></item><item><title>Qwen3.8-27B Q8_0 vs Q4_K_M</title><link>https://orkun.soylu.me/posts/2026-08-18-qwen38-27b-q8-vs-q4/</link><guid>https://orkun.soylu.me/posts/2026-08-18-qwen38-27b-q8-vs-q4/</guid><pubDate>Tue, 18 Aug 2026 00:00:00 GMT</pubDate><description>Dropping from Q8_0 to Q4_K_M on my W7800 bought 29% faster generation and 12 GB of VRAM — far less than the bandwidth maths promised — and made long-prompt prefill 7% slower.</description><category>quantization</category><category>qwen</category><category>ollama</category></item><item><title>Is the AI memory crisis waiting at the door of SAP HANA hardware refreshes?</title><link>https://orkun.soylu.me/posts/2026-08-05-ai-memory-crisis-sap-hana/</link><guid>https://orkun.soylu.me/posts/2026-08-05-ai-memory-crisis-sap-hana/</guid><pubDate>Wed, 05 Aug 2026 00:00:00 GMT</pubDate><description>Memory prices keep breaking records. A thought experiment on what that means for refreshing in-memory SAP HANA servers and for HANA capacity in the cloud.</description><category>sap</category><category>hana</category><category>dram</category><category>cloud</category></item><item><title>Max context in 48 GB: five models</title><link>https://orkun.soylu.me/posts/2026-07-06-vram-fit-48gb/</link><guid>https://orkun.soylu.me/posts/2026-07-06-vram-fit-48gb/</guid><pubDate>Mon, 06 Jul 2026 00:00:00 GMT</pubDate><description>With one model loaded at a time, both Qwen3.6 models get their full 262K context entirely in VRAM on my W7800. Gemma 4 31B doesn't — above 64K it spills to the CPU.</description><category>vram</category><category>ollama</category><category>gemma</category><category>qwen</category></item><item><title>Qwen3.6 35B-A3B MoE vs 27B @26k token prompt</title><link>https://orkun.soylu.me/posts/2026-07-06-moe-vs-dense-long-context/</link><guid>https://orkun.soylu.me/posts/2026-07-06-moe-vs-dense-long-context/</guid><pubDate>Mon, 06 Jul 2026 00:00:00 GMT</pubDate><description>On my 48 GB W7800 the mixture-of-experts model generates 3.4× faster than the dense 27B. Filling a quarter of the context barely dents generation speed — almost all of the wait is prefill.</description><category>moe</category><category>long-context</category><category>vram</category><category>ollama</category></item></channel></rss>
