---
date: 2026-06-12
artifact_type: 5090-share-kit
status: distribution-ready
canonical: https://bmdpat.com/5090-reports
latest_artifact: https://bmdpat.com/5090-reports/latest.md
failure_artifact: https://bmdpat.com/5090-reports/failures/2026-06-12-gemma4-26b.md
email_cta: https://bmdpat.com/5090-reports
linkedin_cta: https://bmdpat.com/5090-reports?utm_source=linkedin&utm_medium=social&utm_campaign=5090-reports&utm_content=share-kit
x_cta: https://bmdpat.com/5090-reports?utm_source=x&utm_medium=social&utm_campaign=5090-reports&utm_content=share-kit
reddit_cta: https://bmdpat.com/5090-reports?utm_source=reddit&utm_medium=social&utm_campaign=5090-reports&utm_content=share-kit
channels:
  - linkedin
  - x
  - r/LocalLLaMA
---

# The 5090 Reports Share Kit - 2026-06-12

Use one draft per post. Keep one artifact and one CTA to the email list.

## Source Artifact

- Hub and email CTA: https://bmdpat.com/5090-reports
- Raw report: https://bmdpat.com/5090-reports/latest.md
- Failure log: https://bmdpat.com/5090-reports/failures/2026-06-12-gemma4-26b.md
- Status: benchmark-failed
- Result: Hardware capture is live. The first bounded Ollama benchmark failed before a valid tokens/sec row, so the public artifact reports the miss instead of inventing a performance claim.

## LinkedIn Draft

The first 5090 Reports artifact is live.

Result: hardware capture works. The benchmark did not. The bounded gemma4:26b run through Ollama timed out before a valid tokens/sec row.

Artifact: https://bmdpat.com/5090-reports/latest.md
Failure log: https://bmdpat.com/5090-reports/failures/2026-06-12-gemma4-26b.md

I am keeping the miss public because local-agent infrastructure needs boring evidence before benchmark claims mean anything.

Get the weekly lab notes: https://bmdpat.com/5090-reports?utm_source=linkedin&utm_medium=social&utm_campaign=5090-reports&utm_content=share-kit

## X Draft

1/ The first 5090 Reports artifact is live.

Hardware capture passed. The benchmark failed before a valid tokens/sec row.

2/ Setup:
RTX 5090
Ollama
gemma4:26b
num_ctx 1024
num_predict 16
5s timeout

3/ Artifact: https://bmdpat.com/5090-reports/latest.md
Failure log: https://bmdpat.com/5090-reports/failures/2026-06-12-gemma4-26b.md

4/ I am publishing the misses too. Local-agent work needs measured runs, failure logs, and cost curves.

Get the weekly lab notes: https://bmdpat.com/5090-reports?utm_source=x&utm_medium=social&utm_campaign=5090-reports&utm_content=share-kit

## r/LocalLLaMA Draft

Title: RTX 5090 local-agent benchmark log: first run captured hardware, Ollama timed out

Body:

I started publishing The 5090 Reports as weekly lab notes for production AI agents on owned hardware.

First public result: no tokens/sec claim yet. The hardware snapshot detected the RTX 5090, but the bounded gemma4:26b Ollama run timed out before a valid benchmark row.

Raw artifact: https://bmdpat.com/5090-reports/latest.md
Failure log: https://bmdpat.com/5090-reports/failures/2026-06-12-gemma4-26b.md

What I am tracking next:

- model, quant, engine, workload
- input and output tokens
- tokens/sec
- watts
- latency
- API-equivalent cost

I am keeping the failed run in the notebook because the boring parts matter: timeouts, VRAM pressure, runner config, and cost curves.

Future reports and the email list are here: https://bmdpat.com/5090-reports?utm_source=reddit&utm_medium=social&utm_campaign=5090-reports&utm_content=share-kit