These scores were compiled from the linked sources. These published scores were not independently tested here. Different prompts, precision, thinking budgets and tools can change results.
IFEval · reported
89.5 / 100
Following precise instructions. These cards report IFEval without consistently specifying prompt-level versus instruction-level scoring. Treat this view as approximate.
Benchmark efficiency: 80.816 published score points per GB of selected weights. This ratio is not an inference-speed measure; check the test settings to see whether the score covers the selected quantization.
Test settings: Publisher evaluation. Settings may differ across models.
Published result for the original model; this selected GGUF file was not separately benchmarked. Different prompts, precision and thinking settings can affect comparisons.
Competition math from AIME 2026. Published answer accuracy.
Benchmark efficiency: 62.666 published score points per GB of selected weights. This ratio is not an inference-speed measure; check the test settings to see whether the score covers the selected quantization.
Test settings: Publisher evaluation. Settings may differ across models.
Published result for the original model; this selected GGUF file was not separately benchmarked. Different prompts, precision and thinking settings can affect comparisons.
Benchmark efficiency: 43.704 published score points per GB of selected weights. This ratio is not an inference-speed measure; check the test settings to see whether the score covers the selected quantization.
Test settings: Publisher evaluation. Settings may differ across models.
Published result for the original model; this selected GGUF file was not separately benchmarked. Different prompts, precision and thinking settings can affect comparisons.
Choosing and calling functions. Published BFCL v4 scores; tool environments and settings differ.
Benchmark efficiency: 42.349 published score points per GB of selected weights. This ratio is not an inference-speed measure; check the test settings to see whether the score covers the selected quantization.
Test settings: Publisher evaluation. Settings may differ across models.
Published result for the original model; this selected GGUF file was not separately benchmarked. Different prompts, precision and thinking settings can affect comparisons.
Writing code to solve scientific problems. Published results can depend on the test scaffold.
Benchmark efficiency: 16.434 published score points per GB of selected weights. This ratio is not an inference-speed measure; check the test settings to see whether the score covers the selected quantization.
Test settings: Publisher evaluation. Settings may differ across models.
Published result for the original model; this selected GGUF file was not separately benchmarked. Different prompts, precision and thinking settings can affect comparisons.
Fixing real software issues with tools. Agent setup and external tools affect these scores. File size covers model weights only.
Benchmark efficiency: 25.554 published score points per GB of selected weights. This ratio is not an inference-speed measure; check the test settings to see whether the score covers the selected quantization.
Test settings: Publisher evaluation. Settings may differ across models.
Published result for the original model; this selected GGUF file was not separately benchmarked. Different prompts, precision and thinking settings can affect comparisons.
These cards say GPQA without naming the variant. Kept separate from confirmed GPQA Diamond results.
Benchmark efficiency: 39.55 published score points per GB of selected weights. This ratio is not an inference-speed measure; check the test settings to see whether the score covers the selected quantization.
Test settings: Publisher evaluation. Settings may differ across models.
Published result for the original model; this selected GGUF file was not separately benchmarked. Different prompts, precision and thinking settings can affect comparisons.
Context and version evidence: The repository and file name identify the selected model. Revision hashes are shown above when recorded. Tested context length, full hardware configuration and run date are not consistently recorded in this snapshot. Only settings explicitly stated in each benchmark record are known.
The 1.107 GB figure covers model weights in this file. It excludes the context cache, runtime, operating system and any separate multimodal files. It is not a measured RAM requirement or a token-generation speed.
These complete configurations pass the initial weight-size check for the selected 1.11 GB file. Allow extra memory for context and software. Check the model’s runtime notes and your inference software before buying.
Listing evidence: 2026-09-25. Amazon.com base price visible in an owner-supplied screenshot reviewed 25 Sep 2026; capture time not supplied. Dated reference, not a live quote. Excludes card signup offers, coupons, tax and shipping.
Listing evidence: 2026-10-03. Apple US launch price announced 22 September 2026: USD 1,699. Dated manufacturer reference, not an Amazon offer; tax and shipping may differ.
Listing evidence: 2026-09-24. GMKtec, EVO-X2 / 64GB / 1TB, recorded 22 Sep 2026; exact ASIN capacity identified 24 Sep. This is a dated reference, not a current Amazon price; tax, shipping and bundle contents may differ.
Memory matches are estimates, not tested compatibility or speed. As an Amazon Associate I earn from qualifying purchases.
Confirm model architecture and quantization support in your runner. The selected weights use 1.107 GB; this excludes context cache, runtime buffers and other programs.
These are the first listed tiers that pass our reserve policy, not measured minimum requirements. System RAM and VRAM remain separate. Use the memory tool to change the reserve for your context and runner.