@QuixiAI: LESSON LEARNED: Always use BF16 kv cache. I was using turboquant. Yeah the VRAM consumption sucks - so another trick is…

X AI KOLs Timeline News

Summary

The author shares a technical lesson on using BF16 KV cache instead of turboquant for AI model optimization and implements CPU offloading in SlimServe for Qwen models to manage VRAM consumption.

LESSON LEARNED: Always use BF16 kv cache. I was using turboquant. Yeah the VRAM consumption sucks - so another trick is to CPU Offload the kv cache. Implemented in SlimServe for 3090 and Qwen (it requires extensive testing to get it right) I have further work to universalize it for all models. I am now evaluating Quen3.8-Flash-Next on Clearwing
Original Article
View Cached Full Text

Cached at: 08/29/26, 12:04 PM

LESSON LEARNED: Always use BF16 kv cache. I was using turboquant.
Yeah the VRAM consumption sucks - so another trick is to CPU Offload the kv cache. Implemented in SlimServe for 3090 and Qwen (it requires extensive testing to get it right) I have further work to universalize it for all models. I am now evaluating Quen3.8-Flash-Next on Clearwing

Eric Hartford (@QuixiAI): My experience with Qwen3.8-Flash-Next is that it can’t even keep track of a multi-turn conversation. It answers questions I asked 2 turns ago. This is at FP8

Similar Articles

16 GB VRAM purgatory discussion thread

Reddit r/LocalLLaMA

A discussion thread sharing configurations and tips for running AI models like Qwen3.8-27B on 16 GB VRAM Windows systems, focusing on memory optimization techniques.