on

Can the NVIDIA RTX Spark N1X (6144-core GPU) (128 GB) run LFM2 1.2B?

26Basic quality (D) · 26 of 100: how capable the model is at F16, whatever it runs on. Match score 54/100 (quality, fit, speed and memory use) sets the ranking.

Yes, it runs great

Runs great. At F16 it needs about 11.2 GB of 102 GB usable, with an estimated speed of 73.8 tok/s.

Best quant
F16
Generation speed
73.8 tok/s
Prompt processing
17,723 tok/s
First token (1K prompt)
0.3 s
Largest safe context
125K

Best app to run it on the NVIDIA RTX Spark N1X (6144-core GPU) (128 GB)

On Linux

vLLM

Inference server · runs on vLLM

  • The full model fits in GPU memory at 8-bit, so it can batch many requests: best for serving a team or an app.
vllm serve LiquidAI/LFM2-1.2B
  • LM Studio Point-and-click: search, download and chat in one window.
  • llama.cpp Usually the first to support new model architectures.

How we choose: the files published for this model, your operating system and GPU, whether it fits fully in memory, and published speed tests (MLX vs llama.cpp on Apple silicon, vLLM vs llama.cpp vs Ollama on NVIDIA). Details.

Download LFM2 1.2B

Recommended for the NVIDIA RTX Spark N1X (6144-core GPU) (128 GB): F16. Every other quantization has its own download link in the table below.

Quantized files · GGUF

Works in LM Studio, llama.cpp, Jan and Ollama. No sign-in needed.

Download the F16 file (opens in a new tab)

huggingface.co/LiquidAI/LFM2-1.2B-GGUF (opens in a new tab)

ollama run hf.co/LiquidAI/LFM2-1.2B-GGUF:F16

Original weights · Hugging Face

Full-precision files from Liquid AI, for fine-tuning, vLLM, Transformers.

huggingface.co/LiquidAI/LFM2-1.2B (opens in a new tab)

No sign-in needed.

Official repo · GitHub

Reference code, inference scripts and docs from Liquid AI. The weights themselves download from Hugging Face.

github.com/Liquid4All/cookbook (opens in a new tab)

Liquid AI’s official cookbook for running LFM models.

git clone https://github.com/Liquid4All/cookbook

Links checked 4 hours ago against Hugging Face, Ollama and GitHub.

How it’s rated

Quality 26Basic quality (D) · 26 of 100: how capable the model is at F16, whatever it runs on. Match score 54/100 (quality, fit, speed and memory use) sets the ranking.
How capable the model itself is at F16, from its editorial quality tier scaled by the quantization or precision. It’s the same on any hardware that runs this variant. Scale: A+ 85+ · A 70+ · B 55+ · C 40+ · D under 40.
Runs Runs great
How well it runs on the NVIDIA RTX Spark N1X (6144-core GPU) (128 GB): speed, capped by how well it fits in memory. Runs great: 30+ tokens/s (or near the image, video or decision speed target) · Runs well: 10+ tokens/s · Slow: 3+ tokens/s · Very slow: under 3 · Won’t run: doesn’t fit even with offload. A tight fit or RAM offload caps it at Runs well; heavy offload caps it at Slow.

Match score

To order lists, each result also gets a match score out of 100 from four parts. It favors the most capable model that still runs well.

Model qualityEditorial quality tier of the model, scaled by the quantization or precision used.11.7 / 45
Memory fitFull marks when the model fits in the share of unified memory the GPU can use; fewer when it goes past that limit.25.0 / 25
SpeedGeneration speed against a 40 tokens/s target for LLMs, or render time against a target for image and video.15.0 / 15
Memory useRewards using the memory you have, so a bigger, better variant beats a tiny one that leaves most memory idle.2.5 / 15
Match score54.2 / 100

The match score orders results; it is not shown as a grade. Quality and Runs are the two ratings in the tables.

Every quantization on the NVIDIA RTX Spark N1X (6144-core GPU) (128 GB)

Quant Memory needed Available Speed Runs Quality Download
Q2_K 9.4 GB 102 GB 517 tok/s Runs great 18Basic quality (D) · 18 of 100: how capable the model is at Q2_K, whatever it runs on. Match score 50/100 (quality, fit, speed and memory use) sets the ranking. GGUF files (opens in a new tab)
Q3_K_M 9.5 GB 102 GB 407 tok/s Runs great 21Basic quality (D) · 21 of 100: how capable the model is at Q3_K_M, whatever it runs on. Match score 51/100 (quality, fit, speed and memory use) sets the ranking. GGUF files (opens in a new tab)
Q4_K_M 9.6 GB 102 GB 315 tok/s Runs great 24Basic quality (D) · 24 of 100: how capable the model is at Q4_K_M, whatever it runs on. Match score 53/100 (quality, fit, speed and memory use) sets the ranking. GGUF (opens in a new tab)
Q5_K_M 9.7 GB 102 GB 260 tok/s Runs great 25Basic quality (D) · 25 of 100: how capable the model is at Q5_K_M, whatever it runs on. Match score 53/100 (quality, fit, speed and memory use) sets the ranking. GGUF (opens in a new tab)
Q6_K 9.9 GB 102 GB 218 tok/s Runs great 25Basic quality (D) · 25 of 100: how capable the model is at Q6_K, whatever it runs on. Match score 53/100 (quality, fit, speed and memory use) sets the ranking. GGUF (opens in a new tab)
Q8_0 10.1 GB 102 GB 160 tok/s Runs great 26Basic quality (D) · 26 of 100: how capable the model is at Q8_0, whatever it runs on. Match score 53/100 (quality, fit, speed and memory use) sets the ranking. GGUF (opens in a new tab)
F16 11.2 GB 102 GB 73.8 tok/s Runs great 26Basic quality (D) · 26 of 100: how capable the model is at F16, whatever it runs on. Match score 54/100 (quality, fit, speed and memory use) sets the ranking. GGUF (opens in a new tab) Original weights (opens in a new tab)

Memory figures assume 8K of context. Longer conversations or documents grow the KV cache.

Other hardware that runs it

Estimates come from published hardware specs and our open formulas, not from running the model on your machine. Real speed varies with runtime, drivers and settings. Numbers marked “Measured” come from a linked benchmark.

Was this page helpful?