82 Billion Tokens. One GPU. 2.7× Faster.
82.5% code understanding. 99.5% verbatim recall. 2.7× faster inference.
Model: Qwen3.6-35B-A3B (Q4 quantized, open weights). Tested on a single RTX 3090 (24 GB VRAM).
Verbatim Reproduction (MRCR v2)
MRCR tests whether a model can find and reproduce exact text from long conversations. The same request is repeated 2-8 times — the model must identify and reproduce the Nth instance verbatim. This is OpenAI's benchmark for long-context quality.
128-256K
256-512K
512K-1M
A 35B open-weight model on a single RTX 3090 outperforms GPT-5.5, Gemini 3.1 Pro, and Claude Opus 4.7 at every context length tested. 99.5% accuracy up to 512K. At 512K-1M, AlphaChat scores 90.7% — beating GPT-5.5 (74%) by +17pp, Opus 4.7 (32.2%) by +59pp, and Gemini 3.1 (26.3%) by +64pp.
MRCR uses SequenceMatcher scoring (0-1 scale). Frontier model scores from published benchmarks (benchlm.ai, llm-stats.com, Anthropic system card). “—” = not publicly benchmarked at that context range. AlphaChat scores measured on identical dataset, same scoring method, using sequential context mode (--context sequential).
Needle in a Haystack: Standard Retrieval vs AlphaChat
10 tests per category, 187 sub-scores per scale. Standard keyword retrieval (BM25) degrades at scale. AlphaChat doesn't.
4M
41M
0.4B
4.1B
20.5B
41B
82B
Corpus size (tokens) →
| Tokens | Standard Retrieval (BM25) | AlphaChat | Delta |
|---|---|---|---|
| 4M | 43.9% | 97.3% | +53.4pp |
| 41M | 49.2% | 95.2% | +46.0pp |
| 0.4B | 30.5% | 98.9% | +68.4pp |
| 4.1B | 28.3% | 96.8% | +68.5pp |
| 20.5B | 28.3% | 94.1% | +65.8pp |
| 41B | 28.3% | 93% | +64.7pp |
| 82B | 28.3% | 92.5% | +64.2pp |
AlphaChat peaks at 98.9% at 0.4B tokens, +68pp over standard retrieval. Maintains 92-99% from 4 million to 82 billion tokens — scale-invariant. Standard keyword retrieval collapses from 44% to 28%.
Code Dependency Understanding (DependEval DR)
DependEval tests whether a model can trace cross-file dependencies in real codebases — which files import from which, what classes depend on what. This is the core skill needed for code navigation, refactoring, and bug tracing. Benchmark: DependEval (ACL 2025), Dependency Recognition task. 2,683 repositories across 8 programming languages.
DependEval DR: Cross-File Dependency Understanding — Accuracy (%)
Previous best: DeepSeek-V3 at 69.7%. AlphaLlama (extended code): +12.8pp over a 671B model.
A 35B model on one GPU outperforms every tested model including DeepSeek-V3 (671B, 19× larger) and all 2026 frontier APIs. AlphaLlama's extended code mode understands cross-file dependencies that raw models miss.
Retrieval at Repository Scale (DependEval Haystack)
Real codebases are large. We tested what happens when you scale DependEval from its original 3K tokens to real repository sizes (10K → 1M tokens).
Code Retrieval at Scale: All Models vs AlphaLlama Extended Code
Codebase size (tokens, log scale) →
Raw Model Performance — Every Model Collapses
| Scale | GPT-5.5 | Gemini 3.1 Pro | Gemma 4 12B | AlphaLlama 35B |
|---|---|---|---|---|
| 100K | 100% | 90% | 0% | 0% |
| 200K | 100% | 0% | 0% | 20% |
| 500K | 50% | 0% | 0% | 0% |
| 1M | 0% | 10% | 0% | 0% |
With AlphaLlama Extended Code Mode — Scale-Invariant
| Scale | AlphaLlama 35B (extended code) | Gemma 12B (extended code) | GPT-5.5 Raw |
|---|---|---|---|
| 10K | 80% | 90% | — |
| 100K | 80% | 90% | 100% |
| 500K | 70% | 80% | 50% |
| 1M | 60% | 70% | 0% |
Extended code mode provides scale-invariant retrieval. While raw models degrade and collapse, AlphaLlama maintains 70-90% accuracy regardless of codebase size.
Key discovery: retrieval ability ≠ comprehension ability. GPT-5.5 is the best at finding code (100% to 200K) but the worst at understanding dependencies (30% DependEval DR). AlphaLlama is the best at understanding (82.5% DR). Extended code mode combines both strengths.
DependEval-Haystack is our benchmark extension. 10 samples per scale, reproducible.
Inference Speed: AlphaLlama vs Ollama
Same model, same GPU, same quantization. AlphaLlama is 2.1-4.6× faster on oversize MoE models thanks to smart offloading.
Test: Qwen3.6-35B (Q4_K_M, 22 GB) on RTX 4080 (16 GB VRAM). Model exceeds GPU memory — overflow handling determines speed.
Short response (2 tok)
4.6×Sustained generation (128 tok)
2.6×Long generation (512 tok)
2.7×Prompt processing
2.1×Ollama
Standard offloading. When a model exceeds GPU memory, performance drops significantly.
AlphaLlama
Smart offloading. Automatically optimizes memory placement to keep the GPU busy. No manual tuning needed — just use -ngl 999.
Ollama version: 0.20 (latest, June 2026). When the model fits entirely in VRAM, both engines perform equally. Speed advantage applies to MoE models that exceed VRAM.
AlphaChat vs SubQuadratic SubQ
SubQuadratic raised $29M and launched SubQ with a 12M token context window.
| Feature | SubQuadratic SubQ | AlphaChat |
|---|---|---|
| Max context | 12M tokens | 82B+ (verified) |
| Accuracy at scale | ~92% (their max at 12M) | 92-99% (4M to 82B) |
| Cost per query | $0.50/MTok (cloud API) | $0 (runs on your GPU) |
| Privacy | Cloud (data uploaded) | Local (data never leaves) |
| Hardware | B200 (cloud) | Consumer GPU (RTX 3090) |
| Open weights | No | Yes |
| Latency at scale | Degrades with context | Constant ~1s |
Speed & Storage
VRAM and RAM stay constant regardless of context size. Scaling is disk-only.
~1s
Query latency (any context size)
127 tok/s
Generation speed (RTX 3090)
~1s is per-query latency against the pre-indexed corpus, not processing 82B tokens live.
| Context Size | Disk | RAM | VRAM |
|---|---|---|---|
| 5B tokens | ~10 GB | 64 GB max | 24 GB max |
| 50B tokens | ~100 GB | 64 GB max | 24 GB max |
| 82B tokens (tested) | 164 GB | 64 GB max | 24 GB max |
| 500B tokens | ~1 TB | 64 GB max | 24 GB max |
Benchmark Methodology
All benchmarks use synthetic needle facts — unique strings that do NOT exist in the model's training data. The model must find the fact in the corpus, not recall it from memory. 6 categories tested, 10 tests per category, 187 sub-scores per scale, 7 scales from 4M to 82B tokens.
| Category | What It Tests |
|---|---|
| Single needle | Find one specific fact in the entire corpus |
| Multi-needle | Find 8+ scattered facts across documents |
| Aggregation | Collect and count items across entire corpus |
| Multi-hop | Chain facts across multiple documents |
| Subtle connection | Link facts with no shared keywords |
| Reasoning | Compare and compute across documents |
82B Token Test Corpus
82 billion tokens across 14 datasets spanning encyclopedic knowledge, code, mathematics, and multilingual text.
| Dataset | Disk Size | Tokens | Domain |
|---|---|---|---|
| Wikipedia (English) | 19 GB | 4.9B | Encyclopedic knowledge |
| NVIDIA Nemotron Post-Training | 42 GB | 10B | General instruction |
| Cascade-RL-SWE | 30 GB | 7.5B | Software engineering |
| RL-Blends | 26 GB | 6.5B | Reasoning & instruction |
| Wenyan (Classical Chinese) | 16 GB | 4B | Multilingual |
| OpenR1-Math | 12 GB | 3B | Mathematics |
| SWE-v1 | 11 GB | 2.7B | Software engineering |
| + 7 smaller datasets | 3 GB | 1B | Mixed |
| Total | 164 GB | ~82B | 14 datasets |
Why Unlimited Context Matters
Code Debugging
FeaturedA large engineering team has 50 billion tokens of codebase, Git history, Jira tickets, PR reviews, Slack threads, and CI logs across hundreds of debugging sessions.
"Trace all issues related to auth_handler.py token handling across all sessions. Find the root cause of the null token crash."
Turns a 3-day debugging marathon into a 5-second query. At $1,000/day, saves $3,000 per incident. 50-person team: $100K+/year.
Legal
A mid-size law firm manages 20 billion tokens of case files, contracts, and court opinions. Standard retrieval sees fragments — AlphaChat reads everything.
"Find all precedents where a non-compete clause was invalidated due to geographic scope across all state courts."
Saves 40+ hours of associate research per complex case. At $300/hour, that’s $12,000 per case.
Medical
A hospital system has 10 billion tokens of patient records, clinical guidelines, drug databases, and research papers.
"Which of this patient’s 12 medications have known interactions with the newly prescribed drug, considering their kidney function and age?"
Prevents adverse drug events. One caught interaction pays for the entire system.
Software Engineering
A large codebase contains 5 billion tokens across 100,000 files, plus documentation and Jira tickets.
"Find all places where the authentication token is passed without encryption, including in third-party libraries."
Finds security vulnerabilities that grep misses (semantic search). A single prevented breach saves $4.5M average.
Research & Academia
A research group has 80 billion tokens of PubMed papers. They need to find connections across the entire literature.
"Which compounds studied for Alzheimer’s have also shown anti-inflammatory properties in rheumatology papers?"
Accelerates drug repurposing research by months. Cross-domain connections lead to breakthrough discoveries.
Enterprise Knowledge
A Fortune 500 company has 100 billion tokens across email archives, wikis, Slack history, and internal databases.
"What decisions were made about the pricing strategy for Product X across all meetings, emails, and documents in the last 2 years?"
Institutional knowledge becomes searchable. Reduces onboarding time by 60%.
Personal AI
A lifetime of personal data: 20 billion tokens of emails, messages, photos (OCR’d), documents, and notes.
"What was the name of that restaurant in Tokyo my friend Sarah recommended last March?"
Perfect memory. Your AI companion remembers everything you’ve ever written, read, or received. Fully local.
AI Model Training
Training frontier AI models requires curating 100+ trillion tokens from thousands of sources. Data quality determines model quality — duplicates waste compute, contamination invalidates benchmarks.
"Find all duplicate passages between CommonCrawl, Wikipedia, RedPajama, and our proprietary corpus. Flag exact and near-duplicate content across all 100 trillion tokens."
Deduplication saves 25-30% of training compute — at frontier scale, that’s $500,000+ per training run.
Data Engineering
A data platform has 500 ETL scripts, 2,000 table definitions, and 10,000 validation rules — 500 million tokens of data infrastructure that no single engineer fully understands.
"Which pipeline cleans the revenue_usd column, and what validation rules apply before it reaches the reporting database?"
Traces data lineage across hundreds of scripts in seconds. Onboards new data engineers 3x faster with instant codebase search.
Data Source
NIAH, MRCR, DependEval, and speed benchmarks. June 2026. Qwen3.6-35B-A3B Q4 on RTX 3090/4080 (24/16 GB VRAM). 82B token corpus (164 GB). DependEval: ACL 2025 benchmark, 2,683 repos, 8 languages. Ollama 0.20.