home
products
contribute
download
documentation
forum
Home
Forums
New posts
Search forums
What's new
New posts
All posts
Latest activity
Members
Registered members
Current visitors
Donate
Log in
Register
What's new
Search
Search
Search titles only
By:
New posts
Search forums
Search titles only
By:
Menu
Log in
Register
Navigation
Install the app
Install
More options
Contact us
Close Menu
Forums
MediaPortal 1
Support
Watch / Listen Media
Television (MyTV frontend and TV-Server)
Timeshift file configuration
Contact us
RSS
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Reply to thread
Message
<blockquote data-quote="mm1352000" data-source="post: 925457" data-attributes="member: 82144"><p>IMO there is not a right or wrong answer here. Yes, you're limited by how many clients you have and how much disk space you have, but within that... you have the freedom to choose what suits you best. So I don't think I agree with the premise that you're starting from, but I've tried to ignore that and filled in the table below with the following assumptions:</p><ol> <li data-xf-list-type="ol">That a person wants the maximal amount of back buffer achievable with the given drive size.</li> <li data-xf-list-type="ol">That the number of clients are the number of people <strong>simultaneously</strong> using the TV Server for timeshifting.</li> <li data-xf-list-type="ol">That a person wants to share the drive size as evenly as possible between the clients.</li> </ol><p>Minimum = maximum due to assumption 1, so I've removed that column.</p><p>I've added "wasted space", which is effectively the amount of space that TV Server can't use because of assumptions 1 and 3 (ie. perfectly even sharing, not first-in-first-served). It does *not* include the amount that TV Server will refuse to use which is always equal to filesize. Obviously, the smaller the filesize, the more space that can be used.</p><p> </p><p>[code]</p><p>Ram Drive | #Clients | File Size | #Minimum | Wasted Space</p><p> </p><p>1024MB 1 128MB 7 0</p><p>1024MB 2 128MB 3 128MB</p><p> </p><p>2048MB 1 128MB 15 0</p><p>2048MB 2 128MB 7 128MB</p><p>2048MB 3 128MB 5 0</p><p>2048MB 4 128MB 3 384MB</p><p> </p><p>4096MB 1 256MB 15 0</p><p>4096MB 2 256MB 7 256MB</p><p>4096MB 3 256MB 5 0</p><p>4096MB 4 256MB 3 768MB</p><p> </p><p>6144MB 1 256MB 23 0</p><p>6144MB 2 256MB 11 256MB</p><p>6144MB 3 256MB 7 512MB</p><p>6144MB 4 256MB 5 768MB</p><p>6144MB 5 256MB 4 768MB</p><p> </p><p>8192MB 1 256MB 31 0</p><p>8192MB 2 256MB 15 256MB</p><p>8192MB 3 256MB 10 256MB</p><p>8192MB 4 256MB 7 768MB</p><p>8192MB 5 256MB 6 256MB</p><p>8192MB 6 256MB 5 256MB</p><p>[/code]</p><p> </p><p>In the cases above where "wasted space" is non-zero, one could modify the filesize slightly to attempt to use the space better as follows:</p><p>[code]</p><p>Ram Drive | #Clients | File Size | #Minimum | Wasted Space</p><p> </p><p>1024MB 2 113MB 4 7MB</p><p> </p><p>2048MB 2 120MB 8 8MB</p><p>2048MB 4 120MB 4 8MB</p><p> </p><p>4096MB 2 240MB 8 16MB</p><p>4096MB 4 240MB 4 16MB</p><p> </p><p>6144MB 2 245MB 12 19MB</p><p>6144MB 3 245MB 8 19MB</p><p>6144MB 4 245MB 6 19MB</p><p>6144MB 5 236MB 5 8MB</p><p> </p><p>8192MB 2 248MB 16 8MB</p><p>8192MB 3 264MB 10 8MB</p><p>8192MB 4 248MB 8 8MB</p><p>8192MB 5 264MB 6 8MB</p><p>8192MB 6 264MB 5 8MB</p><p>[/code]</p><p> </p><p>The general rule is [Disk Space] - [Filesize] >= [# Clients] * [Filesize] * [Minimum].</p><p> </p><p>To maximise the use of disk space you must minimise the difference between the two sides.</p><p>However, you don't want to go too small on the [Filesize] variable as that creates overhead.</p><p>I also note that obviously you're not going to get exactly 1024, 2048, 4096, 6144 and 8192 MB available to Windows after partitioning the space, therefore you probably need to deduct half a dozen or so MB from the noted filesize in each case. For example, assuming a 1024 MB RAM disk has actual partition size of 1000 MB, you're going to want to use 125 MB as the filesize.</p><p> </p><p>Is that what you wanted?</p></blockquote><p></p>
[QUOTE="mm1352000, post: 925457, member: 82144"] IMO there is not a right or wrong answer here. Yes, you're limited by how many clients you have and how much disk space you have, but within that... you have the freedom to choose what suits you best. So I don't think I agree with the premise that you're starting from, but I've tried to ignore that and filled in the table below with the following assumptions: [LIST=1] [*]That a person wants the maximal amount of back buffer achievable with the given drive size. [*]That the number of clients are the number of people [B]simultaneously[/B] using the TV Server for timeshifting. [*]That a person wants to share the drive size as evenly as possible between the clients. [/LIST] Minimum = maximum due to assumption 1, so I've removed that column. I've added "wasted space", which is effectively the amount of space that TV Server can't use because of assumptions 1 and 3 (ie. perfectly even sharing, not first-in-first-served). It does *not* include the amount that TV Server will refuse to use which is always equal to filesize. Obviously, the smaller the filesize, the more space that can be used. [code] Ram Drive | #Clients | File Size | #Minimum | Wasted Space 1024MB 1 128MB 7 0 1024MB 2 128MB 3 128MB 2048MB 1 128MB 15 0 2048MB 2 128MB 7 128MB 2048MB 3 128MB 5 0 2048MB 4 128MB 3 384MB 4096MB 1 256MB 15 0 4096MB 2 256MB 7 256MB 4096MB 3 256MB 5 0 4096MB 4 256MB 3 768MB 6144MB 1 256MB 23 0 6144MB 2 256MB 11 256MB 6144MB 3 256MB 7 512MB 6144MB 4 256MB 5 768MB 6144MB 5 256MB 4 768MB 8192MB 1 256MB 31 0 8192MB 2 256MB 15 256MB 8192MB 3 256MB 10 256MB 8192MB 4 256MB 7 768MB 8192MB 5 256MB 6 256MB 8192MB 6 256MB 5 256MB [/code] In the cases above where "wasted space" is non-zero, one could modify the filesize slightly to attempt to use the space better as follows: [code] Ram Drive | #Clients | File Size | #Minimum | Wasted Space 1024MB 2 113MB 4 7MB 2048MB 2 120MB 8 8MB 2048MB 4 120MB 4 8MB 4096MB 2 240MB 8 16MB 4096MB 4 240MB 4 16MB 6144MB 2 245MB 12 19MB 6144MB 3 245MB 8 19MB 6144MB 4 245MB 6 19MB 6144MB 5 236MB 5 8MB 8192MB 2 248MB 16 8MB 8192MB 3 264MB 10 8MB 8192MB 4 248MB 8 8MB 8192MB 5 264MB 6 8MB 8192MB 6 264MB 5 8MB [/code] The general rule is [Disk Space] - [Filesize] >= [# Clients] * [Filesize] * [Minimum]. To maximise the use of disk space you must minimise the difference between the two sides. However, you don't want to go too small on the [Filesize] variable as that creates overhead. I also note that obviously you're not going to get exactly 1024, 2048, 4096, 6144 and 8192 MB available to Windows after partitioning the space, therefore you probably need to deduct half a dozen or so MB from the noted filesize in each case. For example, assuming a 1024 MB RAM disk has actual partition size of 1000 MB, you're going to want to use 125 MB as the filesize. Is that what you wanted? [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
MediaPortal 1
Support
Watch / Listen Media
Television (MyTV frontend and TV-Server)
Timeshift file configuration
Contact us
RSS
Top
Bottom