Skip to content

AI model catalog

Current model inventory and app wiring. Official FP8 was verified live on both cards on 2026-09-06. The medium fallback is the Git-declared policy; verify it after the reasoning-policy PR reconciles. The capacity audit records runtime evidence and limits.

Declared GPU ownership

Backend Replicas Cards per pod Served model Status
vLLM 1 2 qwen3.8-27b Official FP8 production
llama.cpp 0 1 qwen3.8-27b Retained GGUF rollback
NInfer 0 1 qwen3.8-ninfer Parked evaluation
ComfyUI / SwarmUI 0 1 Image generation Parked

Both RTX 3090s belong to vLLM. Other GPU workloads must remain parked; GPU scale-swap owns the procedure. Flash Next remains a researched alternative.

Official Qwen3.8-27B FP8

Property Value
Engine stock vLLM v0.28.0, pinned digest
Weights official Qwen/Qwen3.8-27B-FP8, pinned revision
Placement TP=2, two RTX 3090s, no CPU weight offload
KV / recurrent state FP8 E4M3 / float16
Context ceiling 262,144 tokens
Concurrency two sequences sharing the KV pool
Vision native encoder; one image per request, video disabled
Reasoning explicit off / low / medium / xhigh; medium default
Speculation disabled; MTP deferred until long-session fixes are validated
Power 220 W per card

The official checkpoint is about 30.89 GB (28.77 GiB). RTX 3090 uses an Ampere-compatible weight-only FP8 path. Host RAM is loading/transport headroom, not additional GPU KV capacity. 262K is a server ceiling, not a promise of two simultaneous full-length sessions. AutoRound INT4/W4A8 is a later speed A/B.

The canonical vLLM runbook owns exact flags, source references, reasoning/sampling examples, rollout checks and rollback. The capacity audit distinguishes smoke checks from performance and sustained quality measurements.

Normal coding uses explicit medium; low is for lighter requests and xhigh is opt-in for difficult tasks. Preservation remains enabled for agents; stateless chats may disable it. Thinking-off requests send both flags false and the separate non-thinking sampler documented in the canonical runbook. Open WebUI normalizes generic high to medium; Pi exposes only valid efforts.

Storage and staging

A Git-pinned manifest records revision, size and SHA-256 for all 77 checkpoint artifacts. A download hook writes the TrueNAS archive, then a cache-sync hook verifies and copies it to local NVMe. The serving init container requires the matching readiness marker and complete file inventory; serving stays offline from local storage. Interrupted downloads resume, while corrupt copies fail verification. Existing AutoRound and GGUF files remain for comparison/rollback.

NAS free space and export write permissions remain rollout checks; local NVMe had approximately 123 GiB free before staging. Follow the vLLM runbook to inspect hooks, health, vision, tools, reasoning and long-context behavior.

App wiring

  • model: qwen3.8-27b
  • application gateway: http://litellm-service.litellm.svc.cluster.local:4000/v1
  • workstation gateway: https://litellm.vanillax.me/v1
  • authentication: namespace-local ExternalSecret from litellm/master_key
  • gateway upstream / diagnostics: http://vllm-service.vllm.svc.cluster.local:8080/v1

All Git-declared local LLM consumers use LiteLLM: Open WebUI, Perplexica/Vane, Presenton, SurfSense, HolmesGPT, Hindsight, Project Nomad, ComfyUI's vision bridge, WorldMonitor, Keep, Deal Scout, Karakeep, News Reader and n8n workflows. Parked replicas and disabled workflows remain parked/disabled. Keep's provider appends /v1/completions itself, so its configured gateway URL omits /v1. The observability runbook covers authentication, persisted settings, ingestion verification and rollback.

The legacy llama.cpp Service still aliases vLLM, and llama.vanillax.me / vllm.vanillax.me remain direct diagnostic routes. Applications must use the authenticated gateway to appear in Langfuse. Direct benchmark probes intentionally bypass gateway telemetry and must not be mistaken for application traffic.

Pi.dev

Pi uses vanillax-vllm/qwen3.8-27b through https://litellm.vanillax.me/v1. Open WebUI uses the in-cluster LiteLLM service. Both routes collect request metrics and Langfuse AI observations; direct vLLM callers bypass that gateway. See AI observability for verification and fallback. The workstation guide owns the provider JSON, explicit medium reasoning mapping, mode-specific sampler extension, compaction reserve, one-image history limit, validation, and rollback. Existing cloud providers remain separate. Start a new session when validating changed defaults.

Historical llama.cpp baseline — 2026-09-03

Normal Open WebUI responses measured about 42-43 generated tok/s. While generating, the single RTX 3090 reported approximately 22,740 MiB / 24,576 MiB VRAM, 87% GPU utilization, and 216 W / 220 W. These are real-machine observations on the Threadripper 2950X host, not synthetic maxima.

Rollback

Revert the FP8 cutover commit through Git, retaining the earlier two-GPU hardware change. This restores llama.cpp's replica, selector Service and route, and parks vLLM. Follow the canonical vLLM runbook for verification. The retained caches avoid another large download.