Refine capacity numbers from LXC 104 summary; flag iGPU passthrough fix
- LXC 104 (docker) confirmed: 16 CPU, 31.25 GiB RAM (7.86 used / 25%), 200 GiB boot disk at 47.7% — disk is the real near-term constraint, not RAM. Numbers propagated into Q11 (docs/11), docs/03 architecture table, and CLAUDE.md infra block. - New optimization #26 in docs/12: fix the Intel Arc iGPU passthrough flagged as broken in the LXC notes. Concrete /etc/pve/lxc/104.conf snippet provided. Once working, TEI / infinity / Immich CLIP can run GPU-accelerated for ~5–10x throughput. - New optimization #27: disk-pressure mitigation playbook (move Qdrant to unas if it grows, prune docker layers monthly, cap n8n executions). - New optimization #28: shrink the LXC's 8 GiB swap to 2 GiB.
This commit is contained in:
@@ -39,7 +39,7 @@ A one-page mental model. For details follow the cross-links.
|
||||
|
||||
| Component | Role | Where it runs (today) |
|
||||
|-----------|------|-----------------------|
|
||||
| **Memos** | Interface, voice input, webhook source | docker host LXC 104 → `memos.nuclide.systems` |
|
||||
| **Memos** | Interface, voice input, webhook source | docker host LXC 104 (unprivileged, 16 CPU / 31 GiB / 200 GiB) → `memos.nuclide.systems` |
|
||||
| **n8n** | Workflow / logic engine | docker host LXC 104 → `n8n.nuclide.systems` |
|
||||
| **SAIA / LiteLLM** | Model gateway, embeddings, classification | docker host LXC 104 → `ai.nuclide.systems` (LiteLLM internal :4000) |
|
||||
| **Qdrant** | Vector memory (semantic recall) | docker host LXC 104 — reuse `qdrant_scientific`. Collections: `nexa_knowledge_text` (Phase 3.1, 1024-dim) and `nexa_knowledge_visual` (Phase 3.2, 768-dim) |
|
||||
|
||||
Reference in New Issue
Block a user