AI Host Optimizer

io.github.williamdoring-prog由 GitHub 帳號 williamdoring-prog 發布v1.2.0更新於 Nov 17, 2026

Profile a host and get an evidence-graded checklist of AI-model optimizations.

發布方自己的服務:Host.al: .al domains and servers in Albania

概覽

AI 產生的概覽

分析本機組態,提供附證據分級的在地 AI 模型推論最佳化清單、方案與基準測試。

可以做什麼
  • 分析主機:作業系統、CPU、記憶體、GPU 與偵測到的工具,僅供讀取
  • 列出最佳化選項及其預估效益、信心等級與資源佔用
  • 為所選選項產生無衝突方案並給出綜合預估
  • 對在地推論的每秒解碼 token 數做基準測試,並提供雜訊下限
  • 檢查登錄檔一致性(開發輔助)
適用情境
適合在在地執行模型(Ollama、llama.cpp、vLLM、Hugging Face)時,判斷哪些調校項目在你这台機器上真的有效,或希望取得實測的前後對照,而非通用建議。
執行需求
透過 npx 以 stdio 在本機執行(需要 Node.js)。未宣告帳號、API 金鑰或環境變數。基準測試會呼叫在地執行環境的 HTTP API,因此量測時需要有一個正在執行的在地推論服務。
安裝前請注意
套用變更會將環境變數檔與啟用指令碼寫入受管理的設定目錄;預設先試跑,可用 revert 還原。在 Linux 上某個選項還會寫入 systemd drop-in,並印出需你自行執行的 root 安裝指令。低於 A 級的估計並非實測,微小差異可能落在本機雜訊下限之內。

安裝

在 SourceWeft 中

  1. 開啟 儀表板中的 AI Host Optimizer,將其新增到工作區。
  2. 為需要使用其工具的對話啟用該服務。

Desktop only,透過 STDIO。 STDIO 服務會啟動本機處理程序,因此需要 SourceWeft 桌面主機。

其他 MCP 客戶端

參照 儲存庫 中的啟動說明。

README

ai-host-optimizer

[npm] [CI] [license: MIT] [MCP Registry]

Profile a host, plan AI-model optimizations, and apply them — reversibly, with consent.

Every "speed up your local LLM" guide lists the same tweaks (Flash Attention, KV-cache quantization, keep-alive, NUMA). The lists are mostly right — they just never tell you which of them helps on your machine, or by how much.

This tool profiles the host, presents the checklist with an honest confidence tier on every number, resolves a conflict-free plan, and — the part that matters — measures the options you apply, with a noise floor, so a null result is reported as a null result instead of a fake win.

It is an MCP server and a CLI. Applying is dry-run by default, writes only into a managed config directory, and is reversible.

Status: 1.2. Profiling and planning are read-only. The applier writes only inside ~/.config/ai-host-optimizer (platform-appropriate), never touches system files, never runs a shell, and never escalates privilege.

Quickstart

bash
npx -y ai-host-optimizer --cli

That prints a read-only profile and the checklist for your machine (trimmed):

Host profile (read-only)  role     : workstation  platform : windows — x64  cpu      : Intel(R) Core(TM) i7-10700K CPU @ 3.80GHz (16 cores)  memory   : 16 GiB total, 8 GiB free  gpu      : nvidia NVIDIA GeForce RTX 3080 (10240 MiB VRAM)  cluster  : 1 GPU(s)  tooling  : ollama, python3, docker
Optimization checklist (read-only)
[ ] Enable Flash Attention  (flash-attention)      improves decode tokens/s: qualitative (tier C)      risk low; fully-reversible; privilege false      stackable: throughput-stack      synergy: kv-cache-quant-q8
[ ] Quantize KV cache to q8_0  (kv-cache-quant-q8)      improves KV cache memory: 50% (tier B)      risk low; fully-reversible; privilege false      ...

Then measure whether a change actually helped:

bash
ai-host-optimizer --benchmark --save-baseline --samples 5   # beforeai-host-optimizer --apply --select flash-attention --yes    # then restart the runtimeai-host-optimizer --calibrate --select flash-attention       # after → tier A, or "no change"

Why

Running local models well depends on host configuration (KV-cache size, Flash Attention, prefix caching, memory/NUMA/swap behaviour, provider prompt caching). The knowledge is scattered across guides. This tool profiles your host and tells you what is worth doing — honestly, labelling each estimate by confidence.

Install

bash
# zero-install (downloads and runs)npx -y ai-host-optimizer --cli
# or globallynpm install -g ai-host-optimizerai-host-optimizer --cli        # or the short alias:  aiho --cli

Usage

bash
# report (read-only)ai-host-optimizer --cliai-host-optimizer --cli --role container
# plan and applyai-host-optimizer --plan  --select kv-cache-quant-q8,keep-alive-preloadai-host-optimizer --apply --select kv-cache-quant-q8,keep-alive-preload          # dry-runai-host-optimizer --apply --select kv-cache-quant-q8,keep-alive-preload --yes    # applyai-host-optimizer --revert
# measure (tier A)ai-host-optimizer --benchmark --save-baseline   # beforeai-host-optimizer --benchmark                   # after (compares to baseline)
# calibrate: measure an option's real effect on THIS host and promote it to tier Aai-host-optimizer --benchmark --save-baseline --samples 5ai-host-optimizer --apply --select flash-attention --yes     # then restart the runtimeai-host-optimizer --calibrate --select flash-attention --samples 5ai-host-optimizer --plan --select flash-attention            # now shows [measured]
# generate declarative accessories from the same registryai-host-optimizer --generate ansibleai-host-optimizer --generate dockerfileai-host-optimizer --generate checklist
# interfacesai-host-optimizer --mcpai-host-optimizer --browser     # browser UI (not yet)ai-host-optimizer --desktop     # desktop UI (not yet)

Applying writes only into the managed directory and prints the source line to activate it. Undo any time with --revert.

What is automated: options with an applyOp. The applier writes one <runtime>.env file per target — ollama.env, llama.cpp.env, huggingface.env, vllm.env — plus a single activate.sh / activate.ps1. On Linux, the ollama-systemd-dropin option additionally writes a systemd drop-in (so the Ollama service actually reads that environment) and prints the root install commands rather than running them. Everything else is advisory: --apply says so plainly rather than doing nothing silently.

Use as an MCP server

Add to your MCP client (e.g. Claude Desktop):

json
{  "mcpServers": {    "ai-host-optimizer": {      "command": "npx",      "args": ["-y", "ai-host-optimizer", "--mcp"]    }  }}

Tools exposed:

ToolPurpose
profileRead-only host profile (OS, CPU, memory, GPU, detected tooling)
checklistOptimization options with estimated improvement + resource footprint
planConflict-free plan for selected ids, with a combined estimate (uses tier-A calibrations when present)
benchmarkMeasure local inference rate (decode tokens/s) + the noise floor — tier-A evidence
validate-registryRegistry consistency check (development aid)

Published to the official MCP Registry as io.github.williamdoring-prog/ai-host-optimizer (see server.json).

Honesty contract

Every estimate carries a confidence tier:

  • A — measured on your host (via --benchmark / --calibrate).
  • B — labelled estimate with a cited method.
  • C — qualitative (direction only, no number).

Tier B/C estimates are never presented as measurements. A combined estimate is only shown once its inputs are trustworthy (see the project plan).

Calibration is honest about noise. --benchmark takes several samples and reports their spread; --calibrate compares before/after and only promotes an option to tier A when the change exceeds the host's own noise floor (the combined run-to-run range). A null result is reported as a null result and records nothing — a small difference inside the noise is not claimed as a win. Use --samples <n> to lower the noise floor when you need to detect a small effect.

What the benchmark measures

--benchmark measures decode tokens/second (and the prefill rate) by calling the local runtime's HTTP API (/api/generate with stream: false), which returns exact token counts and durations rather than a wall-clock guess. It takes several samples, discards a warm-up model load, and reports the median plus the run-to-run spread.

That spread is the whole point. Inference timing on a desktop is noisy — on a test host the spread was ±7% run-to-run, so a single before/after comparison can show a "15% improvement" that is pure noise. So --calibrate refuses to claim a change smaller than the combined spread of the two measurements, and prints a null result as a null result:

  baseline: qwen2.5-coder:14b, 10.29 tok/s, 2638.9 ms, 5549 MiB free  current : qwen2.5-coder:14b, 10.16 tok/s, 2860.5 ms, 5541 MiB free  noise floor: ±13.9%
No significant change: decode tokens/s -1.3% is within the ±13.9% noise floorof this host.Nothing recorded — a null result is not evidence of an improvement.

A tool that will tell you "this didn't help" is more useful than one that always claims a win.

Safety

  • Read-only by default. Profiling and planning never change anything.
  • The applier writes only into the managed config directory (~/.config/ai-host-optimizer, or the platform equivalent) — never system files — runs no shell, and escalates no privilege.
  • Applying is dry-run first: --apply shows the change; --yes performs it.
  • Everything applied is reversible with --revert (and --revert is idempotent).
  • Options are tagged with risk, reversibility and privilege needs.
  • Mutually exclusive options (e.g. KV-cache q8_0 vs q4_0; zram vs disk swap) are one-of groups; stackable options are marked stackable.
  • Role-aware: a container cannot tune the host kernel; a cluster-node is advisory-only.

Roadmap

  • M0 — read-only profiler, registry, checklist, CLI + MCP. ✅
  • M1 — reversible applier (user-space), plan/apply/revert, on-host benchmark. ✅
  • M1b — measured tier-A calibration (median-of-samples benchmark, noise floor, per-option promotion). ✅
  • M1c — multi-runtime applier: one <runtime>.env per target (Ollama, llama.cpp, Hugging Face), 8 applyable options, idempotent revert. ✅
  • M1d — more apply ops: a systemd-dropin op (Ollama service env on Linux, install commands printed not run) and the vllm runtime. 32 options, 11 applyable. ✅
  • M2 — accessory generation (Ansible/Dockerfile/checklist). ✅ (generation)
  • M2b — distribution: official MCP Registry entry live (io.github.williamdoring-prog/[email protected]) + CI publish workflow; directory listings next. 🚧
  • M4 — browser UI and Tauri desktop UI. (planned)

Documentation

Contributing

Contributions are welcome — especially new optimization options and corrections to unsupported claims. See CONTRIBUTING.md for the dev setup and the registry contribution rules. Participation is governed by CODE_OF_CONDUCT.md.

Licence

MIT. See LICENSE.

來源:README.md,提交 b8ae19f

工具

0
SourceWeft 尚未在沙箱中啟動過該軟體包,因此其工具未知。

版本歷史

1
  1. v1.2.0最新Nov 17, 2026

評分

已滿足適用檢查項的 50%

該評分衡量此收錄條目的完整程度,依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價,也不表示伺服器安全或目前可用:可連通性是帶日期的檢查結果,評分也不包含安裝量或使用者評價。

  • 近 30 天內可連通25 分

    請保持端點能夠回應 MCP 握手;SourceWeft 每 30 天探測一次。

  • 已宣告認證方式10 分

    請在註冊中心條目中宣告憑證請求標頭,或保持端點能夠回應探測,以便判定其認證方式。

  • 已列出工具15 分

    請讓伺服器在無憑證時回應 tools/list,或發布可在沙箱中無憑證啟動的軟體包。

  • 描述必需15 分
  • 圖示10 分
  • 文件15 分
  • 授權條款10 分

其他 Host 整合