UkisAI Squeezes Swift 1.5's 27B Reasoning Model Into 8.42GB for Consumer GPUs

UkisAI released compact 2-bit and 3-bit GGUF quantizations of Swift 1.5 that run a 27B reasoning model in under 10GB while cutting thinking tokens by more than half.

·
·
·
UkisAI Squeezes Swift 1.5's 27B Reasoning Model Into 8.42GB for Consumer GPUsPRO
Read2 min
TypeModel
TopicLlms · Gpus
  • UkisAI released mixed-precision GGUF quantizations of Swift 1.5 Qwen3.8-27B ranging from 8.42GB to 11.77GB
  • Swift 1.5 uses 58.5% fewer thinking tokens while scoring 0.35% higher than the base model
  • Four tiers (IQ2_XS, IQ2_S, IQ3_XXS, IQ3_S) each with optional multi-token prediction head variants
  • Built on GSQ and RCO methods from ISTA-DASLab with Swift-specific refinement
  • Compatible with llama.cpp, Ollama, LM Studio, vLLM, and Docker Model Runner out of the box
  • Distributed under Swift Open License v1.0, not Apache 2.0, so enterprise users should check terms

UkisAI compresses Swift 1.5 27B into an 8.42GB GGUF

UkisAI has released four mixed-precision GGUF versions of Swift 1.5, a post-trained Qwen3.8-27B reasoning model. The smallest model file occupies 8.42GB, lowering the storage and memory requirements for local inference on consumer GPUs and unified-memory Macs.

The release combines per-tensor bit allocations from ISTA-DASLab’s quantization research with a Swift-specific calibration and refinement process. UkisAI reports that the resulting files track the BF16 model’s token probabilities more closely than its initial Swift quantizations across prose, code, mathematics and multilingual test data.

Two sets of efficiency claims

Swift 1.5 itself provides the first efficiency gain. According to UkisAI, the full-precision post-trained model uses 58.5% fewer reasoning tokens than its Qwen base while scoring 0.35% higher across the cited tasks, producing a reported 9.18× speed-up on several evaluations.

Those figures apply to the full-precision Swift 1.5 model. The GGUF release adds weight compression, but the model card does not report equivalent downstream task scores or end-to-end speed measurements for every quantized tier. Its quantization results focus primarily on distribution similarity.

Four files trade size for fidelity

Each tier assigns different bit widths to individual tensors according to their sensitivity. The reported file sizes and development-set Kullback-Leibler divergence, or KLD, are:

Tier File size Development KLD

Pro article

This story is for Pro members

You've reached the end of the free preview. Upgrade to AlphaSignal Pro to read the full article - and everything else behind the paywall.

Trending
  • No trending articles

Comments

avatar

Next Reads