club-5060ti refresh: tested RTX 5060 Ti presets, a proper high-context harness, and Qwen3.8 27B

Quick update on the RTX 5060 Ti local LLM repo. It has changed quite a bit since my previous posts. The project started as a collection of practical notes and benchmark results. That was useful, but as the dataset grew it became harder to answer the question most people actually had: What configuration should I run? I have rebuilt the repo around tested, copyable presets rather than treating every successful benchmark request as a front-page result. What changed? The project now separates three things: • Presets: exact configurations intended for people to copy and run. • Evidence bundles: reviewed proof of context fit, retrieval, sustained generation and performance. • Raw receipts: retries, failed experiments and diagnostic runs that are kept separate as engineering material without automatically becoming recommendations. The website now leads with the published preset catalogue. The larger results explorer is still there for comparisons and historical data, but it is no longer the first thing visitors have to decipher. There are currently seven published presets across the 1× and 2× RTX 5060 Ti lanes: 1× RTX 5060 Ti 16GB • Qwen3.8 27B IQ3_XXS at 64K with q8 KV and built-in MTP • ThinkingCap Qwen3.6 27B IQ3_M at 64K • Nail 35B-A3B IQ3_XXS on a configured 131K route 2× RTX 5060 Ti 16GB • Qwen3.8 27B Q6_K at 131K • ThinkingCap Qwen3.6 27B Q6_K at 131K • Nail 35B-A3B Q4_K_XL at 131K • Muse Glimmer 30B dynamic Q4 at 131K with DFlash The 1× and 2× lanes are what I can test locally, not a ceiling for the project. The data model and contribution path still support 3×/4× setups, mixed GPUs and other CUDA hardware, provided the topology and serving configuration are reported clearly. The new high-context harness A large configured context size is not enough to call a preset validated. The new harness calibrates prompts against the model’s actual tokenizer, disables prompt caching, gives each request a unique nonce, and repeats both: • long-context retrieval near the tested context tier; • sustained generation that must produce enough work and reach a client-visible answer. Failed tiers and incomplete runs are recorded rather than quietly converted into recommendations. The scripts can produce a candidate report, but they cannot assign recommended status or publish it automatically. This has already caught several cases where a model technically loaded at a large context but either failed retrieval, stopped inside hidden reasoning, or could not reliably produce visible output. Qwen3.8 27B results The recommended single-card route is currently: • IQ3_XXS • 64K context • q8 KV • built-in MTP, n=2 • approximately 29.8 tok/s sustained decode at a 45.9K-token prompt • two uncached retrieval and two sustained visible-answer checks passed For two cards, Qwen3.8 27B Q6_K is now the recommended dense route: • 131,072 context • f16 KV • 50/50 tensor split • built-in MTP, n=2 • two retrieval checks passed at approximately 115.4K prompt tokens • two sustained checks passed at approximately 91.8K prompt tokens • both sustained runs generated 3,072 tokens and reached visible answers • approximately 597.9 tok/s prefill • approximately 38.6 tok/s sustained decode The harness originally gave thinking models a 1,536-token output allowance. Qwen3.8 could spend most of that budget reasoning without reaching its visible answer, so the allowance is now separate from the minimum generated-work requirement. That gives thinking-heavy models room to finish without weakening the actual pass threshold. The 131K result is the highest tier tested for this preset, not a claim about the model’s absolute maximum context. Measurement caveat The seed results were measured with both GPUs core clocks locked at 2300 MHz and the stock 180W power limit. That is my normal quieter operating point and makes the runs more reproducible, but stock-boost or overclocked cards may be faster. Repo: https://github.com/5p00kyy/club-5060ti Preset catalogue and evidence explorer: https://5p00kyy.github.io/club-5060ti/ Contributions are welcome, including reproductions, failed fit checks, mixed-GPU setups and larger 5060 Ti configurations. The boring details matter: exact model, quant, context, KV cache, runtime, topology, prompt length, generated tokens and serving flags. submitted by /u/do_u_think_im_spooky [link] [comments]

Source: r/LocalLLaMA | 2026-08-15

Related