A wiki about
the practice.
Anyone can buy VRAM. Nobody can buy a setup that works.
vram.wiki documents what people actually do with local language models: the hardware, the stack, the task and the result.
This project was born from an r/LocalLLM thread in September 2026.
I’m QuantumCrafty on Reddit, the person maintaining this project. I curate the dataset, review contributions and shape the tools around it. If you want to reach me personally, Reddit is the best place to start.
This project is free and independent. If it saved you a weekend of trial and error, buy me a coffee — it genuinely helps keep the wiki running.
Genesis: a useful starting point
The original Genesis dataset was manually extracted and carefully rewritten from the detailed comments in that thread. It preserves real experiences that would otherwise disappear into a long conversation, but it is necessarily incomplete: commenters did not all provide the same level of hardware, model, performance, or workflow detail.
These entries are kept as an attributed, read-only record of where the project began — not as a claim that every field is perfectly comparable. When a detail was not stated, it stays unknown.
How the Genesis dataset was built
Genesis was assembled in two collection phases, then checked before publication:
- Initial capture. Relevant answers were read manually through old.reddit and selected when they contained enough concrete detail to be useful.
- Enrichment. The Arctic Shift API was used later to retrieve complementary context and make the source material easier to process.
- Cleaning and structure. Noise was removed, duplicates were grouped, and each case was shaped into comparable fields for hardware, models, runtimes, workflows, results and limits.
- Human review. Ambiguities were corrected, missing facts stayed unknown, and only reviewed snapshots entered the published dataset.
Cloud AI assistance can help with extraction and rewriting in this workflow. It does not decide what gets published or fill in facts that were never stated. A future local Ollama pipeline can use the same contracts and review gates.
A living dataset from v1
New setups now come directly through the vram.wiki contributor space. They are submitted as dated snapshots, reviewed before publication, and can be revised by their owners as the hardware and workflow evolve. Over time, these richer first-party contributions will become the primary layer of the directory, while Genesis remains available as community context.
This is a community-built record.
The people who shared those answers are what make the dataset useful. If you see your setup here, thank you — and please correct or extend it if anything is missing.
Our most important rule
When a detail is not stated, it stays unknown. No VRAM guessed from a GPU name, no invented usernames, no promises turned into facts.
Share without an account
Use the Tally form for a one-off contribution. No GitHub sign-in is required, and your response enters the same human review queue.
Open the anonymous formKeep a private history
Use the dashboard or an MCP-compatible agent to follow review status and propose future updates under your account.
Share through dashboardSuggest an improvement