d1-omni-600M

A 587M dense checkpoint from LiquidAI only earns a slot on disk if Q4 at a usable context fits the card you already own. d1-omni-600M local is the listing for that decision, not a cloud demo.

I care about what the official card actually promises, whether d1-omni-600M holds a usable quant and context on your GPU, and where it tends to disappoint once the weights are on disk.

What d1-omni-600M is

The weights live at LiquidAI/d1-omni-600M on Hugging Face. That repo is the source of truth for license (other), config, tokenizer, and file names. This directory does not host the blobs.

Architecture is dense. Stored parameters decide disk and load size. If this is a mixture-of-experts row, active parameters decide tokens per second; do not mix those two numbers.

From the official card, trimmed: --- library name: transformers license: other license name: lfm1.0 license link: LICENSE language: - en - de - es - fr - it - nl - pl - pt - ar - hi - ja - ru - tr - vi - zh pipeline tag: image-text-to-text base model: LiquidAI/LFM2.5-Encoder-350M tags: - liquid - lfm2.5 - edge - decision - classification - calibration - system-one - multimodal -

vision - audio --- Try LFM • Docs • VRAM calculator says it does not fit, believe the calculator before a social-media screenshot.

Check the repo siblings for GGUF. If none exist, convert from safetensors or wait for a community quant.

Use Q4_K_M as the default local quant. Go Q5 or Q6 only after you have headroom. Go Q3 or IQ2 only if you accept more quality loss to stay on a small card.

When you first load d1-omni-600M, watch nvidia-smi or Activity Monitor. Shared GPU memory climbing is the same as a failed fit, even if the process stays alive.

Tokens per second track memory bandwidth. A 4090 and a 3060 12 GB can both load a 7B–8B Q4; they will not feel the same at 8k context.

d1-omni-600M on a local stack is a hardware decision first. If the card cannot hold the quant you want, pick a smaller sibling or a higher compression — do not keep retrying the same file.

How people actually use it

For chat, keep a short system prompt and a fixed sampler. Changing temperature every test makes local A/B comparisons useless.

For coding, prefer a GGUF that matches the instruct template the authors shipped. A base model with a chat wrapper bolted on will look worse than the same weights with the right template.

For RAG, context window is not free. Retrieval dumps that fill 16k tokens will evict the system prompt on a card that only holds 8k comfortably.

Do not treat missing composite scores as missing capability. Scores appear after two sourced benchmarks with URLs. Until then the listing still has VRAM math and the official card.

If you later add sourced MMLU, LiveCodeBench, or similar numbers, they show in the benchmark table with links. Until a URL exists, this page will not invent a score.

Keep the how-to page for install steps. This deep dive is for whether d1-omni-600M belongs on your machine and what you should expect once it does.

If you still need a shortlist by GPU size, start from What can I run and filter by the card you already own before opening another listing.

What to watch for

Sampler defaults differ across UIs. A “creative” preset in one frontend can look like a broken model next to llama.cpp defaults. Lock temperature, top-p, and the chat template before you compare.

Thinking-mode checkpoints (when the card documents them) spend tokens on a hidden chain of thought. That is extra VRAM and latency, not free quality. Turn the mode off if you only wanted a fast chat reply.

Unofficial quants can ship the wrong tokenizer or a stripped chat template. If replies are garbage after a clean load, check the template before you blame the GPU.

Long-context claims on the card still have to fit KV cache. YaRN or similar extensions do not magically add VRAM. Drop context first when the process dies at 16k.

Driver and runtime updates change tokens per second more often than weight revisions do. Re-run one fixed prompt after a CUDA or llama.cpp bump.

If you serve d1-omni-600M on a LAN, treat it like any other unauthenticated app: private bind, no port-forward, auth if more than one person can reach it.

This listing will not rank d1-omni-600M against closed APIs. Local means the weights are on disk and the meter is your wall power, not a vendor invoice.