Reply to thread

Message

<blockquote data-quote="kerpow" data-source="post: 82912" data-attributes="member: 20978">That would depend on a few things, like how physically big your server is, ie how many disks you can mount.&nbsp; If you have a massive HP NetServer with external raid arrays (which I guess you don't, I am making a point) then you may as well stick with that.I think you need to consider your network.&nbsp;&nbsp; Imagine you are watching TV with time-shift on a client Media Server.&nbsp; Your data will go from the server, to your NAS, from the NAS to the client and all of that will have to go through one switch/hub/box.&nbsp; While this may well be within the bounds of the network infrastructure the data is real time and any glitches in the stream will play out on screen (or get saved to disk).&nbsp;&nbsp; I have seen this before, working with MPEG2 streams in a gigabit broadcast environment (over IP) while the network should have handled the data fine, small switching delays etc can play havoc with real time data (granted glitches do also occur in disk buffers etc).The bottom line is that IP was never interned for real time streams, there are some products out there that attempt to prioritise IP traffic for this very purpose (ie InfoValue) but they have no place in a home network.The best thing you can do is over speck the network, and under-run the application, ie; stick with your on-board RAID unless you need more space than you can fit.&nbsp; Unless that is you can install an ATM network at home (<a href="http://cgi.ebay.com.au/ws/eBayISAPI.dll?ViewItem&amp;item=150044125520&amp;ssPageName=ADME:B:EF:US:2" target="_blank">http://cgi.ebay.com.au/ws/eBayISAPI.dll?ViewItem&amp;item=150044125520&amp;ssPageName=ADME:B:EF:US:2</a>) with true QoS, mmmmm, nice).Cheers <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite1" alt=":)" title="Smile&nbsp; &nbsp; :)" loading="lazy" data-shortname=":)" /></blockquote>

[QUOTE="kerpow, post: 82912, member: 20978"] That would depend on a few things, like how physically big your server is, ie how many disks you can mount. If you have a massive HP NetServer with external raid arrays (which I guess you don't, I am making a point) then you may as well stick with that. I think you need to consider your network. Imagine you are watching TV with time-shift on a client Media Server. Your data will go from the server, to your NAS, from the NAS to the client and all of that will have to go through one switch/hub/box. While this may well be within the bounds of the network infrastructure the data is real time and any glitches in the stream will play out on screen (or get saved to disk). I have seen this before, working with MPEG2 streams in a gigabit broadcast environment (over IP) while the network should have handled the data fine, small switching delays etc can play havoc with real time data (granted glitches do also occur in disk buffers etc). The bottom line is that IP was never interned for real time streams, there are some products out there that attempt to prioritise IP traffic for this very purpose (ie InfoValue) but they have no place in a home network. The best thing you can do is over speck the network, and under-run the application, ie; stick with your on-board RAID unless you need more space than you can fit. Unless that is you can install an ATM network at home ([url]http://cgi.ebay.com.au/ws/eBayISAPI.dll?ViewItem&item=150044125520&ssPageName=ADME:B:EF:US:2[/url]) with true QoS, mmmmm, nice). Cheers :) [/QUOTE]

Verification