Provider marketing loves big connection numbers because they fit on comparison tables. In SABnzbd and NZBGet, a connection is simply a parallel SSL session pulling different article segments from the same NNTP host. More sessions can raise throughput until something else becomes the bottleneck: home router CPU, Wi-Fi, disk write speed, or your downloader host struggling to decrypt traffic. Understanding that ceiling saves money on plans you cannot physically use and prevents misconfigured fill servers from hogging resources. Use this guide while tuning setups described in best provider for SABnzbd.
What one Usenet connection actually does
When you set connections to thirty, the client opens thirty parallel NNTP channels to the server you configured. Each channel fetches pieces of the files referenced by your NZB. Providers publish a maximum allowed per account tier; exceeding it can trigger throttling or temporary blocks.
Connections apply per server entry. Primary at priority zero and fill at priority one each maintain their own pools if you configure both actively.
How many connections to use at home
Start between twenty and fifty percent of your plan maximum on typical home hardware, then increase while watching download speed and error counters. If speed flatlines but CPU pegs, you found the local limit, not a reason to switch brands.
Raise in steps of five or ten, not jumps to the brochure cap. Note whether gains appear on large season packs versus small jobs; both matter for Sonarr automation.
Where throughput dies before the provider does
SSL decryption on NAS and Pi hardware often caps sessions before a gigabit ISP line saturates. Spinning disks on incomplete volumes stall par expand. Wi-Fi backhaul to a downloader in a closet adds latency that mimics distant farms.
When speed is low despite moderate connections, inspect CPU, disk utilisation, and path MTU issues before opening more sessions.
Plan maxima: unlimited vs block accounts
Flagship unlimited plans advertise high connection caps. Block and promotional tiers sometimes publish lower maxima even under the same brand. Read the status page for your exact product.
Do not run primary and fill both at their respective maxima on weak boxes simultaneously. That doubles SSL load for marginal completion gains.
Fill servers deserve fewer connections
Optional fill exists to retrieve missing articles after the primary exhausts what it has. Configure fill with a smaller connection count so it sips bandwidth and CPU until needed. Flooding fill turns an insurance policy into a default download path that drains block gigabytes.
Stack theory and priority rules live in primary and fill Usenet. Remember independent backbones for fill; twin Highwinds accounts are not fill.
Practical tuning checklist in SABnzbd
Set SSL on port 563, enable fill as optional at priority one, and cap connections per server. After ISP or hardware changes, rerun a short test NZB before trusting old numbers. IPv6 only helps when your provider documents working endpoints and your router path is stable; otherwise stay on IPv4 without guilt.
Log completion misses for a week before buying fill capacity. Connections fix speed problems; they rarely fix indexer or backbone mismatch alone.
On Synology and Unraid hosts, revisit connection caps after major DSM or Unraid upgrades because Docker CPU limits and default ulimits occasionally change. A setting that worked pre-upgrade is worth revalidating with one manual NZB before Sonarr dumps a backlog.
Mobile hotspot tests are poor proxies for fixed homelab results. Always tune against the downloader that will run twenty-four seven on your LAN.
FAQ
- Does unlimited connections mean infinite?
- No. Marketing language still maps to a numeric cap in account details.
- Why am I slow at only ten connections?
- Could be ISP shaping, disk, Wi-Fi, or distant routing; raise carefully while monitoring CPU.
- Should fill match primary connection count?
- Usually no; fill should stay lower unless logs show sustained need.
- Do more connections improve completion?
- Not directly. Completion is retention and takedown timing; connections affect parallel fetch speed.
- Can I set connections above the plan max?
- Do not; servers may reject or throttle sessions.
Related
- Usenet on Raspberry Pi
- Usenet on Synology
- SABnzbd setup guide
- Highwinds twins are not fill
- Provider matrix