Has anyone seen Infuse on Apple TV/iPad pull way more WebDAV bandwidth than the actual file size / watched portion?
I’m using Infuse with TorBox WebDAV. TorBox counts outgoing WebDAV traffic, so I’ve been watching usage closely.
A few data points:
-
Mac Infuse test: I downloaded 10.5GB through Infuse, and TorBox increased from 834GB → 845GB. So basic WebDAV accounting seems correct.
-
Adding an 11GB cached folder to Infuse only increased usage by ~1GB, so merely adding cached content doesn’t seem to be the issue.
-
But on Apple TV, I watched about 1.5 episodes of TV via WebDAV. Each episode is ~1.1GB, so even if Infuse downloaded both full files, I’d expect ~2.2GB usage. Instead, TorBox went from 846GB → 872GB, a +26GB increase.
My Infuse settings are now conservative:
-
Auto Scan: Off
-
Pre-Cache Details: Off
-
Pre-Cache Artwork: Off
-
Smart Folders: Off
-
Streaming Cache: Limited
TorBox support shared backend logs showing large WebDAV transfers tied to the file hashes, so it looks like Infuse/Apple TV may actually be requesting far more data than expected.
Has anyone else seen Apple TV/iPad + WebDAV aggressively re-request chunks, buffer huge amounts, or generate bandwidth far above the file size? Any settings or debugging tips I should try?