Skip to content

What's new in 2.x2.x

Both versions speak the same SABnzbd API and serve the same WebDAV paths, so Arrs and media servers see no difference.

Feature1.x2.x
In both
SABnzbd API for ArrsYesYes
WebDAVYesYes
Symlink and STRM importsYesYes
Health checks and Arr replacementYesYes
Multiple providers with priority levelsYesYes
Download speed limitYesYes
Disk segment cacheYesYes
SQLite and PostgreSQLYesYes
Prometheus metricsYesYes
New or changed in 2.x
Mountrclone sidecarBuilt-in FUSE
Provider catalog with backbonesNoYes
Only in 1.x
PAR2 repairYesNot yet
Connection cap across all providersYesNot yet
Stremio and addon routesYesNot yet
Search, indexers and ProwlarrYesNot yet
Backup and restoreYesNot yet
Watchtower, Preflight and WardenYesNot planned

The upgrade report lists every 1.x setting it could not carry over. Rclone RC notifications and cache flags are dropped; the built-in mount does not need them.

1.x is written in C# and runs on .NET. 2.x is written in Rust. For a server that spends its time moving bytes from Usenet to a player, that shows in a few places:

  • One native binary. The server, the web UI and the FUSE mount ship as one compiled program. There is no runtime to load and no code to warm up, so 2.x starts in under half a second.
  • No garbage collector. Rust frees memory as soon as it goes out of use, and nothing pauses to collect garbage. Idle memory stays near 70 MB.
  • Less CPU per byte. Streaming 1 GB costs under a third of the CPU time it does on 1.x.
  • Memory safe. The compiler rules out use-after-free bugs and data races. The only unsafe code in infinidysk itself is the binding to the SIMD yEnc decoder.
  • 12× faster startup
  • 3× less CPU per GB streamed
  • 2× less memory at idle

1.x is C# on .NET; 2.x is Rust. Lower is better. Bars show the range across three passes.

Startup

1.x6.2 s
2.x0.4–0.5 s

CPU time per GB streamed

1.x13.2–13.3 s
2.x3.7–4.1 s

Memory at idle

1.x165–302 MB
2.x68–70 MB

Memory per stream

1.x1.28–1.53 GB
2.x1.14–1.26 GB

Sequential throughput is on par within run-to-run variance: 103–111 MB/s on 1.x, 92–103 MB/s on 2.x. Neither version rebuffered in five plays at a 3.1 MB/s playback rate.

Measured on 27 October 2026 with 1.6.3 and 2.0.0-alpha.8 in Docker on one Apple M4 Pro host, one commercial provider with 20 connections, five posts with a median size of 10.7 GB, three passes.