Reply to thread

Message

<blockquote data-quote="Owlsroost" data-source="post: 1143381" data-attributes="member: 83973">As mm has explained, the 'under the hood' logic is simple (assuming all timeshifting is on the same drive):Maximum possible total timeshift file usage (per server) = available disk space on timeshift drive - one file size.Minimum space required per client stream = min timeshift files x file size.Maximum space required per client stream = max timeshift files x file size.Timeshifting will not work correctly (for a stream) unless there is always sufficient disk space for (min timeshift files x file size) per stream.There is no 'friendly sharing' between the timeshifting processes - it's a free-for-all competition in terms of getting available disk space.(I'm being careful here referring to 'client streams' because MP2 has Picture-in-Picture support, so could have 2 streams per client).</blockquote>

[QUOTE="Owlsroost, post: 1143381, member: 83973"] As mm has explained, the 'under the hood' logic is simple (assuming all timeshifting is [B]on the same drive[/B]): Maximum possible total timeshift file usage (per [B]server[/B]) = available disk space on timeshift drive - one file size. Minimum space required per client stream = min timeshift files x file size. Maximum space required per client stream = max timeshift files x file size. Timeshifting will not work correctly (for a stream) unless there is always sufficient disk space for (min timeshift files x file size) per stream. There is no 'friendly sharing' between the timeshifting processes - it's a free-for-all competition in terms of getting available disk space. (I'm being careful here referring to 'client streams' because MP2 has Picture-in-Picture support, so could have 2 streams per client). [/QUOTE]

Verification