on

Can the UP Squared Pro 7000 (16 GB) run Flow Judge v0.1?

64Good quality (B) · 64 of 100: how capable the model is at Q8_0, whatever it runs on. Match score 63/100 (quality, fit, speed and memory use) sets the ranking.

Barely: it runs very slowly

Very slow. At Q8_0 it needs about 6.1 GB of 8.0 GB usable and makes one decision in about 36.8 s.

Best quant
Q8_0
Time per decision
36.8 s
Decisions per second
0.0/s
Input assumed
1,024 tokens
Returns
Written feedback, then a score

Best app to run it on the UP Squared Pro 7000 (16 GB)

On Windows

llama.cpp

Command line + local API · runs on llama.cpp

  • Supports Intel Arc through SYCL and Vulkan.
  • Usually the first to support new model architectures.
llama-server -hf flowaicom/Flow-Judge-v0.1-GGUF:Q8_0
  • LM Studio Point-and-click: search, download and chat in one window.
  • Jan Point-and-click: search, download and chat in one window.

On Linux

llama.cpp

Command line + local API · runs on llama.cpp

  • Supports Intel Arc through SYCL and Vulkan.
  • Usually the first to support new model architectures.
llama-server -hf flowaicom/Flow-Judge-v0.1-GGUF:Q8_0
  • LM Studio Point-and-click: search, download and chat in one window.
  • Jan Point-and-click: search, download and chat in one window.

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 Flow Judge v0.1

Quantized files · GGUF

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

huggingface.co/flowaicom/Flow-Judge-v0.1-GGUF (opens in a new tab)

ollama run hf.co/flowaicom/Flow-Judge-v0.1-GGUF

Original weights · Hugging Face

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

huggingface.co/flowaicom/Flow-Judge-v0.1 (opens in a new tab)

No sign-in needed.

Links checked 3 days ago against Hugging Face, Ollama and GitHub.

How it’s rated

Quality 64Good quality (B) · 64 of 100: how capable the model is at Q8_0, whatever it runs on. Match score 63/100 (quality, fit, speed and memory use) sets the ranking.
How capable the model itself is at Q8_0, 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 Very slow
How well it runs on the UP Squared Pro 7000 (16 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.

PrecisionEditorial precision tier from the model’s published benchmarks, scaled by the quantization or precision used.28.8 / 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
SpeedTime for one decision against a 100 ms target: reading the input plus any tokens the model writes.0.8 / 15
ClarityHow easy the answer is to use in code: a probability or score earns the most, written feedback before a score the least.9.0 / 15
Match score63.6 / 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 UP Squared Pro 7000 (16 GB)

Quant Memory needed Available Speed Runs Quality Download
Q4_K_M 4.4 GB 8.0 GB 21.5 s Very slow 60Good quality (B) · 60 of 100: how capable the model is at Q4_K_M, whatever it runs on. Match score 62/100 (quality, fit, speed and memory use) sets the ranking. GGUF (opens in a new tab)
Q5_K_M 4.8 GB 8.0 GB 24.8 s Very slow 62Good quality (B) · 62 of 100: how capable the model is at Q5_K_M, whatever it runs on. Match score 62/100 (quality, fit, speed and memory use) sets the ranking. GGUF files (opens in a new tab)
Q6_K 5.2 GB 8.0 GB 28.5 s Very slow 63Good quality (B) · 63 of 100: how capable the model is at Q6_K, whatever it runs on. Match score 63/100 (quality, fit, speed and memory use) sets the ranking. GGUF files (opens in a new tab)
Q8_0 6.1 GB 8.0 GB 36.8 s Very slow 64Good quality (B) · 64 of 100: how capable the model is at Q8_0, whatever it runs on. Match score 63/100 (quality, fit, speed and memory use) sets the ranking. GGUF files (opens in a new tab)
F16 9.7 GB 8.0 GB 85.4 s Very slowfar over GPU memory limit 64Good quality (B) · 64 of 100: how capable the model is at F16, whatever it runs on. Match score 42/100 (quality, fit, speed and memory use) sets the ranking. GGUF (opens in a new tab) Original weights (opens in a new tab)

Times are for one request with a 1,024-token input and about 150 tokens written. Batching servers process many requests at once.

Other hardware that runs it

Quick answers

How much memory does Flow Judge v0.1 need on the UP Squared Pro 7000 16GB?

At Q8_0 it needs about 6.1 GB. The UP Squared Pro 7000 16GB has 8.0 GB usable.

How fast is Flow Judge v0.1 on the UP Squared Pro 7000 16GB?

It makes one decision in about 36.8 s at Q8_0, an estimate from the hardware and the size of the model.

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?