<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Hugging-Face on Technical Notes</title><link>http://luispa.com/en/tags/hugging-face/</link><description>Recent content in Hugging-Face on Technical Notes</description><generator>Hugo -- 0.148.0</generator><language>en-US</language><lastBuildDate>Sun, 22 Feb 2026 00:00:00 +0000</lastBuildDate><atom:link href="http://luispa.com/en/tags/hugging-face/index.xml" rel="self" type="application/rss+xml"/><item><title>Limiting Hugging Face Bandwidth</title><link>http://luispa.com/en/posts/2026-02-22-limitar-hf/</link><pubDate>Sun, 22 Feb 2026 00:00:00 +0000</pubDate><guid>http://luispa.com/en/posts/2026-02-22-limitar-hf/</guid><description>&lt;img src="http://luispa.com/img/posts/logo-shaping.svg" alt="Bandwidth Limiting Logo" width="150px" height="150px" style="float:left; padding-right:25px" />
&lt;p>Downloading LLM models locally is something you do occasionally, but when you pull a massive 122B parameter model like &lt;code>Sehyo/Qwen3.5-122B-A10B-NVFP4&lt;/code>, the download hogs the entire connection and leaves the rest of the household without internet. The Hugging Face CLI (&lt;code>huggingface-cli&lt;/code> or &lt;code>hf&lt;/code>) doesn&amp;rsquo;t have a &lt;code>--limit-rate&lt;/code> flag, so you need to find alternatives. In this post I explain two ways to limit bandwidth on Linux using Docker (my preferred method) or Wondershaper at the host level.&lt;/p>
&lt;br clear="left"/></description></item></channel></rss>