Skip to content
Tagged articles

AVX-512

8 articles · Page 1 of 1
DataFunSummit
DataFunSummit
Nov 15, 2026 · Artificial Intelligence

284B DeepSeek on 64GB CPU: Quantization Works, 96GB Xeon Fails on AVX-512

The llama-modchip project runs a 284B-parameter DeepSeek-V4-Flash model on a 64GB RAM CPU-only machine via aggressive quantization to 1.71 bits/weight (56.56 GiB), achieving 9–10 tokens/sec, but a 96GB Xeon server fails due to custom GGUF tensor types and missing AVX-512, highlighting hardware-software compatibility gaps.

AVX-512CPU inferenceDeepSeek-V4-Flash
0 likes · 13 min read
284B DeepSeek on 64GB CPU: Quantization Works, 96GB Xeon Fails on AVX-512
DataFunTalk
DataFunTalk
Nov 8, 2026 · Artificial Intelligence

DeepSeek-V4-Flash on 64GB CPU: Why 96GB Xeon Can't Load It

The article explains how llama-modchip runs 284B DeepSeek-V4-Flash on a 64GB RAM CPU-only machine via aggressive quantization (1.71 bits/weight), while a 96GB Xeon server fails due to tensor format mismatch and missing AVX-512. It breaks down inference latency for long contracts (~10 minutes for 20k tokens) and proposes three evaluation metrics: time to first token, key-field extraction accuracy, and total processing time.

AVX-512CPU inferenceDeepSeek-V4-Flash
0 likes · 12 min read
DeepSeek-V4-Flash on 64GB CPU: Why 96GB Xeon Can't Load It
Rust High-Frequency Quantitative Trading
Rust High-Frequency Quantitative Trading
Apr 14, 2026 · Backend Development

How SIMD Powers Ultra‑Low‑Latency High‑Frequency Trading with Rust

The article explains SIMD fundamentals, traces the evolution of x86 instruction sets, compares Intel and AMD implementations, examines the controversy around AVX‑512, and shows how Rust leverages SIMD to accelerate critical paths in high‑frequency quantitative trading, offering concrete code examples and performance tips.

AVX-512CPU optimizationRust
0 likes · 19 min read
How SIMD Powers Ultra‑Low‑Latency High‑Frequency Trading with Rust
BirdNest Tech Talk
BirdNest Tech Talk
Oct 31, 2025 · Backend Development

How Go’s New Green Tea GC Slashes CPU Overhead by Up to 40%

The article examines Go 1.25’s experimental Green Tea garbage collector, explains why the traditional mark‑sweep approach hurts modern CPUs, details the page‑oriented redesign and its AVX‑512 vector acceleration, and shows how these changes can cut GC‑related CPU usage by 10‑40%.

AVX-512Garbage CollectionGo
0 likes · 7 min read
How Go’s New Green Tea GC Slashes CPU Overhead by Up to 40%
Java Backend Technology
Java Backend Technology
Jul 26, 2020 · Fundamentals

Why Linus Torvalds Wants AVX-512 Gone: Inside Intel’s Power‑Hungry Instruction Set

Linus Torvalds lambasts Intel’s AVX‑512 extension as a ‘power virus’, arguing it bloats CPUs, serves only niche benchmarks, and harms everyday performance, while noting Intel’s recent move to limit AVX‑512 to large cores in Alder Lake and recalling his past clashes over Intel’s security patches.

AVX-512CPU performanceInstruction Set
0 likes · 7 min read
Why Linus Torvalds Wants AVX-512 Gone: Inside Intel’s Power‑Hungry Instruction Set
21CTO
21CTO
Jul 18, 2020 · Fundamentals

Linus Torvalds Demands AVX-512’s End: Intel’s Power‑Hungry Extension Hurts Users

Linus Torvalds publicly denounced Intel’s AVX‑512 instruction set, calling it a ‘power‑virus’ that bloats CPUs for niche benchmark gains, urging Intel to abandon it in favor of simpler, more efficient code that benefits everyday users rather than specialized high‑performance scenarios.

AVX-512CPU architectureIntel
0 likes · 6 min read
Linus Torvalds Demands AVX-512’s End: Intel’s Power‑Hungry Extension Hurts Users