Research-doc index: current vs. superseded #57
Notifications
Due Date
No due date set.
Blocks
#60 Target doc structure
haylan/LLM-Server
Reference: haylan/LLM-Server#57
Reference in new issue
Block a user
Part of #55
Question
For each file in docs/research/, classify it as current (still describes the running stack) or superseded by X (LiteLLM-era, replaced choice, removed feature), with a one-line reason. Image-generation docs are marked for deletion. AFK. Output: the index table in the resolution comment.
Resolution: docs/research/ index
Checked each doc against
docker-compose.yml(llama-server Qwen3.8-27B, qwen-classifier Qwen3-4B, OmniRoute, lazytainer, qdrant, neo4j). "Linked from" = grep hits outsidedocs/research/.docs/server-planing.mdas superseded context, so the two docs conflict (see note 3)qwen-classifier, notllama-server-fast, and the quant is Q4_K_XL, not Q8_0. Sizing moved to classifier-context-window-scaling.mdOMNIROUTE_DIRECT_HEADERS_TIMEOUT_MS) plus the ROCm stall incident. That key is not set in compose/.env.example today--cache-reuse/LLAMA_PARALLELandSTREAM_IDLE_TIMEOUT_MSsettings in compose:8080. The live setup goes through OmniRoute, per docs/coding-cli-setup/opencode.mddownloader-fast) was fixed in78adbf4. The rest are either done or folded into #56/#61config.yamlmodel_info, which no longer exists. The Sonnet reference-price choice is only history now; nothing implements shadow costLLAMA_MODEL_FILEin compose--jinja). Clients now reach the model through OmniRoute's/v1/messages, not llama.cpp's shim, but the parser finding still appliesGPU_MAX_HW_QUEUES=1+ numericgroup_addGIDs fixes are live on llama-server and qwen-classifier. The doc saysllama-server-fast, which is nowqwen-classifierTotals: 15 CURRENT (4 with drift noted), 9 SUPERSEDED, 2 DELETE.
Notes for execution:
docs/server-planing.mdsuperseded, but #55 says keep server-planing.md. The index should say which build plan is active. Flag for #56/#60.