b70-optimization-lab

Qwen3 30B-A3B Instruct 2507 UD-Q4_K_XL Rapid Snapshot

Audience: benchmark readers and future optimizers who need the first strict-valid one-B70 llama.cpp baseline for this model.

Status

Headline Strict Row

Use the plain cache-disabled recipe as the representative row. A few sub-percent runtime variants landed near 108 tok/s, but did not repeat beyond noise.

Same-recipe / same-family support rows:

Conclusion: keep the simple default recipe for this rapid result. The quick screen found no reproducible knob win worth changing the recipe.

Reproduce

cd /home/steve/llm-optimizations

MODEL=/mnt/usb-models/llm-models/qwen3-30b-a3b-instruct-2507-gguf/Qwen3-30B-A3B-Instruct-2507-UD-Q4_K_XL.gguf \
MODEL_ALIAS=qwen3-30b-a3b-instruct-2507-udq4-rapid \
LABEL=qwen3-30b-a3b-instruct-2507-udq4-llamacpp-faon-nocacheprompt-realistic128 \
GPU_INDEX=0 PORT=19630 \
CTX_SIZE=4096 BATCH_SIZE=1024 UBATCH_SIZE=256 \
FLASH_ATTN=on CACHE_TYPE_K=f16 CACHE_TYPE_V=f16 \
MAX_TOKENS=128 METRIC_TOKENS=100 \
scripts/run-rapid-llamacpp-realistic-candidate.sh

The runner defaults REQUEST_EXTRA_JSON to {"cache_prompt":false} for llama.cpp rapid strict runs. Do not remove that for headline claims; the first diagnostic run with llama.cpp’s default prompt-cache behavior reported cached_tokens=3 after the first prompt and is invalid for fresh-response throughput.

Validity

This row uses the shared rapid realistic suite:

The benchmark uses streamed text/reasoning deltas for token timing because llama.cpp does not provide vLLM-style streamed token IDs here. All rows emitted enough streamed deltas for the 100-token metric window.

Blocked vLLM/GPTQ Path

The official Qwen/Qwen3-30B-A3B-GPTQ-Int4 file was downloaded and validated locally under:

/mnt/usb-models/llm-models/qwen3-30b-a3b-gptq-int4

It did not serve on the current local vLLM/XPU build. Startup failed before readiness because the build lacks GPTQ ops such as _C.gptq_shuffle, gptq_gemm, gptq_marlin_repack, and marlin_gemm. This is a runtime-support blocker, not a benchmark result. A later recovery lane should try a newer Intel/vLLM XPU build or container before dismissing GPTQ for this model.