The name is the button.

An agent writes the code now, and a human thumb hovers over Accept all a hundred times a day. The honest question of this decade is what, exactly, you just accepted. So I read the diff.

Eight years as a backend engineer in Stockholm, back in Tokyo since 2023, and I still ship something small most nights, usually badly. My one rule: the only real review of a model is the thing you built with it. That is why there is no leaderboard on this site.

Around a hundred and forty sources come through — the labs' own posts, the papers, the tools, the runtimes and languages nobody is watching yet, the chip under the demo, and the newsletters people actually forward. What is moving gets counted so the week reads at a glance, and every few days I explain one mechanism in plain words.

A story here is a headline, a short excerpt, one image and the link to whoever wrote it. We never reproduce the post; the images belong to their authors. A post written in Japanese appears in Japanese, exactly as it was published, and the link goes to the original.

— Yuki Halvorsen, Tokyo

← Accept All Archive

Hugging Face BlogLabs

Impactful scheduling for GPU clusters

October 9

Building a cluster scheduler to prioritize high-impact research while maintaining full occupancy

Chips & compute

Read at Hugging Face Blog ↗

One letter a week, starting soon.

Latest

Impactful scheduling for GPU clusters

Related

LabsHolo4: powering generalist computer-use agents Hugging Face Blog

LabsFine-tuning a 350M Model for Better Structured Outputs in 100 GRPO Steps Hugging Face Blog

LabsIntroducing @huggingface/kernels: 200+ WebGPU Kernels for Local AI Hugging Face Blog

Toolsb11530: llama: keep the backend sampling graph static across ubatches (#30223) llama.cpp releases

GitHubAmazon ECS now auto-repairs failing GPUs and instances. Here’s why it matters for SREs. The New Stack

SiliconPC shipments tumble over 20% in 3Q26 as chip shortages bite Tom's Hardware