I run open models on my own GPUs and publish the results.

Each report shows the model, quant, prompt, hardware, speed, VRAM use, and what broke. AgentGuard handles spend limits, loops, timeouts, and rate limits.

Read the 5090 Reports Subscribe to the journal

RTX 5090 / TEST 01saved

GENERATION

228.9TOK/S

PEAK VRAM

7.8GB

QUANT

Q4_K_MGGUF

RTX 5090 run. llama3.1:8b, Q4_K_M, tested 2026-07-09.

Selected run01 / 06

Model: llama3.1:8b
Quant: Q4_K_M
Generation: 228.9 TOK/S
Peak VRAM: 7.2 GB

Open all six measured rows

Measured benchmark rows from the 2026-07-09 sweep
Model	Quant	Workload	Gen tok/s	Prompt tok/s	Peak VRAM
llama3.1:8b	Q4_K_M	short-gen-256	228.9	679	7.2 GB
llama3.1:8b	Q4_K_M	long-context-summarize	206.7	12,109	7.8 GB
llama3.1:8b	Q4_K_M	agent-code-task-512	227.8	1,028	7.8 GB
gemma4:26b	Q4_K_M	short-gen-256	198.8	15 (cold)	19.9 GB
gemma4:26b	Q4_K_M	long-context-summarize	180.2	6,179	20.2 GB
gemma4:26b	Q4_K_M	agent-code-task-512	207.4	197	20.2 GB

Fig. 1 Six runs on the RTX 5090, Ollama 0.31.1, temperature 0. llama3.1:8b Q4_K_M reached 228.9 tok/s generation, measured 2026-07-09.Raw artifact

Changing num_ctx between requests forces a full model reload. On a 26B that is 140 seconds per swap. Pin your context size.
Field note, 2026-07-09

Each report includes the model, quant, prompt, hardware, and result. Failed runs stay up too. The June timeout that preceded this test is still in the archive.

Read the 5090 Reports

§ 002 / Safety checks