Signal-3.8-27B-GGUF: Faster and More Token-Efficient

September 18, 2026

Signal-3.8-27B-GGUF: Faster and More Token-Efficient

At a Glance

Item Value
Repository agentionai/Signal-3.8-27B-GGUF
Published 2026-09-10
License apache-2.0
Formats GGUF
Paper arXiv:2606.00206
Source type Primary source (the publisher itself)

Values determined by this site’s code at collection time. Dates are JST.

Overview

agentionai/Signal-3.8-27B-GGUF is a GGUF model created by minimally invasively fine-tuning the base model Qwen3.8-27B to operate with lower generation latency and higher token efficiency. In general prompt evaluations, it successfully reduces response tokens by 57% and reasoning tokens by 52% while maintaining answer quality equal to or better than the base model. This allows it to complete processing in less than half the wall time of the base model on equivalent hardware.

Specifications

  • License: apache-2.0
  • Parameters: 27.8B

Performance

According to the model card evaluations, compared to the base model Qwen3.8-27B Q8_0, Signal significantly reduces response and reasoning tokens. Below are the measured results of token changes in general prompts and coding.

base Q8_0 Signal change
general answers, median tokens 243 104 -57%
answers opening with a preamble (“Sure!", “Great question") 13% 0% gone
answers with markdown headers 47% 18% -62%
answers with bold 85% 52% -39%
coding answers, median tokens 159 142 -11%
coding answers, p90 tokens 1026 914 -11%

Token counts during the thinking mode were also measured.

base Q8_0 Signal change
reasoning tokens, general prompts, median 153 74 -52%
reasoning tokens, coding prompts, median 225 166 -26%
reasoning tokens, GSM8K, median 119 81 -32%

Exact match quality on GSM8K (a benchmark measuring step-by-step arithmetic word problem solving at the elementary school level) is as follows:

base Q8_0 Signal
thinking off, 60 problems 98.3% 98.3%
thinking on, 40 problems 92.5% 95.0%

Additionally, speed comparisons using speculative decoding are as follows:

prompt / draft length base acceptance Signal acceptance decode speed vs base
prose, draft 3 39% 47% +10%
prose, draft 4 35% 28% -9%
structured output (JSON), draft 3 72% 94% +20%
structured output (JSON), draft 4 66% 87% +22%
chat prompts, sampled at 0.7, adaptive draft ≤4 (40 prompts) 57% 60%

The performance of the original model Qwen3.8-27B has also been measured across various benchmarks. A partial excerpt of the text performance comparison table is as follows:

→ Scroll horizontally to see all columns

Qwen3.8-27B Qwen3.6-27B Qwen3.7-Plus Muse Glimmer-30B Opus4.6 Max
Coding
Agentic terminal coding Terminal Bench 2.1 (Terminus) 73.0 63.4 64.0 51.7 78.2
Agentic coding SWE-bench Pro 61.7 53.5 57.6 51.2 53.4
Repo-level code generation NL2Repo-Bench 42.3 36.2 41.1 47.6
Agentic coding DeepSWE 1.1 42.2 13.3 14.2
Software engineering QwenSWEBench 79.0 49.3 59.2 63.8
Agent
Long-horizon office work CoWorkBench 70.7 61.0 65.1 68.2
Professional job tasks JobBench 33.4 21.8 27.6
Frontier agentic tasks Agents’ Last Exam Pass@1 20.4 Score 42.9 Pass@1 10.6 Score 27.3 Pass@1 13.2 Score 33.6
General
Instruction following IFBench 79.5 69.1 79.1 77.0 62.5
Scientific reasoning GPQA Diamond 89.2 87.8 90.3 83.5 91.3
Multidisciplinary reasoning HLE 30.8 24.0 34.7 22.0 40.0
Competitive coding LiveCodeBench v6 90.3 83.9 89.6 88.8

These figures show that while maintaining the base model’s excellent knowledge, reasoning capabilities, and high potential in code generation and agent tasks, Signal achieves significant speedups and improved token efficiency by stripping away unnecessary preambles and redundant reasoning steps.

Strengths and Use Cases

Signal is a fine-tuned model of Qwen3.8-27B designed to achieve lower generation latency and higher token efficiency. It cuts down on token usage without sacrificing answer quality by providing direct answers and omitting unnecessary preambles, excessive formatting, greetings, and explanatory narration. Furthermore, even in thinking mode, it reduces the tokens used to explain the process while preserving useful reasoning steps. It also retains the image input capabilities (vision encoder and projector) inherited from the base model.

Hardware Requirements

Estimated requirements (calculated by Local Model Watch) — 27.8B parameters (taken from the base model Qwen/Qwen3.8-27B)

Your VRAM Quantization File size Est. memory needed
16GB (RTX 5060 Ti 16GB / 4060 Ti 16GB, etc.) IQ4_XS 13.3GB 15.9GB
24GB (RTX 4090 / 3090, etc.) Q5_K_M 18.2GB 21.8GB
32GB (RTX 5090, etc.) Q6_K 20.9GB 25.1GB
48GB (RTX 6000 Ada / A6000, etc.) Q8_0 27.1GB 32.5GB

Memory estimates add a 20% runtime overhead (KV cache, etc.) to the actual size of the distributed files. Actual usage varies with context length, batch size and inference engine. These figures are computed by this site from file sizes, not published by the model’s authors. Compare with other models in our VRAM quick reference. What the quantization names mean: glossary.

How to Get It

  • Distribution format: GGUF
  • Supported engines: llama.cpp (llama-server, etc.), Ollama, LM Studio

Example command for running with llama.cpp:

llama-server -hf agentionai/Signal-3.8-27B-GGUF:AP-Q4_K_XL \
  --jinja -ngl 999 -fa on -c 32768 \
  --temp 0.7 --top-p 0.95 --top-k 20 --min-p 0

To add the built-in draft head to increase throughput, append the following arguments (requires a build supporting --spec-type draft-mtp):

  --spec-type draft-mtp --spec-draft-n-max 4

Note that when using image inputs, download and use mmproj-BF16.gguf (0.87 GiB) for the base model located at the root of the repository together with any tier.

Related Articles

Sources