Execution & hardware / FEATURE

CPU inference

Documented CPU execution path; no minimum performance implied.

2connected products
Explore in graph ↗

Standing condition: these are documentation claims at the source capture date, with outcome “claimed”; no runtime execution is recorded. Dossier applicability and limitations apply throughout. Expand a row for its statement, specific scope and contradictions. Numbered citations resolve to the source locator and capture date below. Missing evidence means Unknown, not No. Sources are unpinned unless marked “Pinned”; this marks source stability, not stronger support or runtime verification. Reuse counts refer to claims in the full dossier; repeated citations do not represent independent sources.

Yes Documented within scope Partial Limited form of the feature No Explicit evidence of absence Unknown No evidence recorded. These are support assessments, not quality scores or runtime verification.

2 products have Yes or Partial documentation. Review freshness and attestation counts describe the dossier, not runtime quality. Gaps below are product-wide, not necessarily specific to this feature.

llama.cpp →

Needs recheck · 2026-10-150 attestations · rev 2026-09-15.1 · unreviewed
CPU inferenceYes
Explore CPU inference →

Documents CPU inference with architecture-specific optimizations.

Scope: Supported model and configured local backend; documentation only, no execution recorded.

2 open gaps · applicability & verification plan

What we do not know yet about llama.cpp

  • Which pinned model, quantization, context length and runtime versions fit the selected Mac?
  • What are measured latency, throughput, peak memory and swap under one and four concurrent requests?

Applicability

Repository revision 38a5b42d9a3e82e0a586bcd1caed121f36c87a73; living documentation separately dated.

Self-managed local build and server; pin compiled backends and model files.

Excludes: Runtime verification and performance rankings; Model weights license or quality evaluation; Cloud inference, remote hosts and external tools; Unlisted model architectures, builds and hardware

Recheck when

  • Runtime, bundled engine, backend, model format or license changes.
  • Documentation changes affecting the cited configuration.

Needs recheck · due

Verification plan

  1. Choose hardware and obtain explicit approval for installations, downloads and execution resources.
  2. Pin runtime and engine versions, model artifact hashes, tokenizer, template, quantization and inference settings.
  3. Run the local-model-mac investigation with synthetic prompts and capture raw measurements; do not record documentation as execution.

Provenance & review

Testedknowhow model runtime research

Commissioned by a Nimbalyst maintainer. Documentation synthesis; no independent review or product execution.

Revision 2026-09-15.1 · unreviewed · checked

0 attestations · Content: Unlicensed prototype; redistribution decision pending

Sources · 1

[1]llama.cpp overview ↗Pinned6 / 13 claims
repository · locator & rights

38a5b42d9a3e82e0a586bcd1caed121f36c87a73

Description; supported backends; quick start

Link and original paraphrase only; upstream rights retained.

MLX-LM →

Needs recheck · 2026-10-150 attestations · rev 2026-09-15.1 · unreviewed

Unknown — no evidence recorded

3 open gaps · applicability & verification plan

What we do not know yet about MLX-LM

  • Which pinned model, quantization, context length and runtime versions fit the selected Mac?
  • What are measured latency, throughput, peak memory and swap under one and four concurrent requests?
  • Concurrency and JSON schema output are Unknown in this research package; no cited absence is asserted.

Applicability

Repository revision 872ae88d1fac77350db23c8c04fe8dd372a9e3e8; living documentation separately dated.

Local Apple Silicon execution with MLX; model conversion and server configuration remain operator-owned.

Excludes: Runtime verification and performance rankings; Model weights license or quality evaluation; Cloud inference, remote hosts and external tools; Unlisted model architectures, builds and hardware

Recheck when

  • Runtime, bundled engine, backend, model format or license changes.
  • Documentation changes affecting the cited configuration.

Needs recheck · due

Verification plan

  1. Choose hardware and obtain explicit approval for installations, downloads and execution resources.
  2. Pin runtime and engine versions, model artifact hashes, tokenizer, template, quantization and inference settings.
  3. Run the local-model-mac investigation with synthetic prompts and capture raw measurements; do not record documentation as execution.

Provenance & review

Testedknowhow model runtime research

Commissioned by a Nimbalyst maintainer. Documentation synthesis; no independent review or product execution.

Revision 2026-09-15.1 · unreviewed · checked

0 attestations · Content: Unlicensed prototype; redistribution decision pending

Ollama (local runtime) →

Needs recheck · 2026-10-150 attestations · rev 2026-09-15.1 · unreviewed
CPU inferenceYes
Explore CPU inference →

Documents CPU execution and GPU offload modes.

Scope: Backend placement can be inspected using ollama ps.

2 open gaps · applicability & verification plan

What we do not know yet about Ollama (local runtime)

  • Which pinned model, quantization, context length and runtime versions fit the selected Mac?
  • What are measured latency, throughput, peak memory and swap under one and four concurrent requests?

Applicability

Repository revision a43fad18b088095de20fbd7a8f0de50824cf5d27; living documentation separately dated.

Local Ollama server with OLLAMA_NO_CLOUD=1 and preloaded local models; excludes Ollama Cloud and web search.

Excludes: Runtime verification and performance rankings; Model weights license or quality evaluation; Cloud inference, remote hosts and external tools; Unlisted model architectures, builds and hardware

Recheck when

  • Runtime, bundled engine, backend, model format or license changes.
  • Documentation changes affecting the cited configuration.

Needs recheck · due

Verification plan

  1. Choose hardware and obtain explicit approval for installations, downloads and execution resources.
  2. Pin runtime and engine versions, model artifact hashes, tokenizer, template, quantization and inference settings.
  3. Run the local-model-mac investigation with synthetic prompts and capture raw measurements; do not record documentation as execution.

Provenance & review

Testedknowhow model runtime research

Commissioned by a Nimbalyst maintainer. Documentation synthesis; no independent review or product execution.

Revision 2026-09-15.1 · unreviewed · checked

0 attestations · Content: Unlicensed prototype; redistribution decision pending

Sources · 1

[2]Ollama FAQ ↗4 / 11 claims
vendor-documentation · locator & rights

Local data; disabling cloud; server binding; concurrent requests

Link and original paraphrase only; upstream rights retained.

LM Studio (local runtime) →

Needs recheck · 2026-10-150 attestations · rev 2026-09-15.1 · unreviewed

Unknown — no evidence recorded

3 open gaps · applicability & verification plan

What we do not know yet about LM Studio (local runtime)

  • Which pinned model, quantization, context length and runtime versions fit the selected Mac?
  • What are measured latency, throughput, peak memory and swap under one and four concurrent requests?
  • The schema has no proprietary source-access value: Not established does not override the explicitly recorded proprietary app terms.

Applicability

Living documentation accessed 2026-09-15; app and installed engine versions are not pinned.

Local LM Studio app and server; pin the separately installed llama.cpp or MLX engine. Excludes remote hosts, Bionic workflows and external tools.

Excludes: Runtime verification and performance rankings; Model weights license or quality evaluation; Cloud inference, remote hosts and external tools; Unlisted model architectures, builds and hardware

Recheck when

  • Runtime, bundled engine, backend, model format or license changes.
  • Documentation changes affecting the cited configuration.

Needs recheck · due

Verification plan

  1. Choose hardware and obtain explicit approval for installations, downloads and execution resources.
  2. Pin runtime and engine versions, model artifact hashes, tokenizer, template, quantization and inference settings.
  3. Run the local-model-mac investigation with synthetic prompts and capture raw measurements; do not record documentation as execution.

Provenance & review

Testedknowhow model runtime research

Commissioned by a Nimbalyst maintainer. Documentation synthesis; no independent review or product execution.

Revision 2026-09-15.1 · unreviewed · checked

0 attestations · Content: Unlicensed prototype; redistribution decision pending

Keep exploring execution & hardware