Hi Infuse Team,
I am writing to report a serious bandwidth waste issue I’ve observed during video playback when the streaming cache mode is set to ‘Auto’.
While streaming a 40-minute episode (approximately 2GB in size), my network packet capture revealed that Infuse ended up consuming a staggering 26GB of data.
Here is the exact behavior I observed:
- The entire video file is successfully cached within the first few minutes of playback.
- However, about 1 minute and 10 seconds after the initial caching is completely finished, Infuse initiates a new HTTP Range request.
- From that point on, roughly every 1 minute, Infuse starts a similar Range request that stays active for about 60 seconds before disconnecting.
- Each of these redundant requests downloads around 500MB of data, leading to the massive total traffic consumption.
This continuous loop creates an enormous and meaningless waste of network traffic. I have tested the exact same video environment with other media players, and they behave as expected: once the video is fully cached, they stop sending any further network requests.
Could you please investigate why Infuse keeps looping these Range requests even after the file is fully buffered? I hope this caching logic can be optimized in a future update.
Thank you for your time and assistance.
I saw a similar issue in a previous article because ‘tickling’ only requests a few bytes, but the request body I captured showed a different result:
Range: bytes=670498161- ,According to the HTTP specification, this means “returning from this position to the end of the file.” The playback node should only return the complete remaining length. However, in the current Infuse 8.4.8, some requests hold for approximately 60 seconds.