<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>High Definition for PC &#187; SAS</title>
	<atom:link href="http://www.hd4pc.com/techblog/tag/sas/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.hd4pc.com/techblog</link>
	<description>Evolving Media Post Production Workflows in Light of Advancing Computer Technology</description>
	<lastBuildDate>Sat, 24 Dec 2011 19:23:32 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
		<item>
		<title>Post Production Media Storage and Drive Arrays</title>
		<link>http://www.hd4pc.com/techblog/2010/12/05/post-production-media-storage-and-drive-arrays/</link>
		<comments>http://www.hd4pc.com/techblog/2010/12/05/post-production-media-storage-and-drive-arrays/#comments</comments>
		<pubDate>Sun, 05 Dec 2010 21:55:02 +0000</pubDate>
		<dc:creator>McCarthyTech</dc:creator>
				<category><![CDATA[Hardware News]]></category>
		<category><![CDATA[Industry Status]]></category>
		<category><![CDATA[Compression]]></category>
		<category><![CDATA[Fibre Channel]]></category>
		<category><![CDATA[PCIe]]></category>
		<category><![CDATA[SAS]]></category>
		<category><![CDATA[SATA]]></category>

		<guid isPermaLink="false">http://www.hd4pc.com/techblog/?p=208</guid>
		<description><![CDATA[After my last article explained why USB3 is not ready to be used as the interface for primary media editing drives, this has led to the question of: what interface should be used for attaching media arrays to editing workstations for maximum system performance?  Even more so than with basic external hard drives, there are [...]]]></description>
			<content:encoded><![CDATA[<p>After my last article explained why <a href="http://en.wikipedia.org/wiki/Usb3#USB_3.0" target="_blank">USB3</a> is not ready to be used as the interface for primary media editing drives, this has led to the question of: what interface should be used for attaching media arrays to editing workstations for maximum system performance?  Even more so than with basic external hard drives, there are a number of competing options, none of which have emerged as clearly superior.  At this point the answer really varies a lot depending on your needs and budget.  It has been three years since my last article on the subject, so the market has changed considerably since then.  The primary options as I see it, are <a href="http://en.wikipedia.org/wiki/ESATA#eSATA" target="_blank">eSATA</a>, <a href="http://en.wikipedia.org/wiki/Serial_attached_SCSI#SAS_vs_SATA" target="_blank">SAS</a>, external <a href="http://en.wikipedia.org/wiki/PCI_Express" target="_blank">PCIe</a>, and <a href="http://en.wikipedia.org/wiki/Fiber_channel" target="_blank">Fibre Channel</a>.  While older parallel <a href="http://en.wikipedia.org/wiki/SCSI" target="_blank">SCSI</a> based devices are technically still available, the interface has no real advantages over even eSATA, let alone the more expensive options.<br />
<span id="more-208"></span><br />
<a href="http://www.bhphotovideo.com/c/search?Ntt=eSATA+array&amp;N=0&amp;BI=6727&amp;KBID=7302" target="_blank">eSATA</a> is of course based on the popular SATA interface, and connects an array of drives to a system in their native interface.  Most <a href="http://en.wikipedia.org/wiki/RAID" target="_blank">RAID</a> redundancy is usually accomplished at the controller level, with a <a href="http://www.bhphotovideo.com/c/search?Ntt=eSATA+PCI&amp;N=0&amp;BI=6727&amp;KBID=7302" target="_blank">PCI expansion card </a>inside the workstation.  Some arrays are capable of creating<a href="http://www.bhphotovideo.com/c/search?Ntt=eSATA+RAID&amp;N=0&amp;BI=6727&amp;KBID=7302" target="_blank"> integrated RAID </a>sets, which are presented to the host system as single large volumes.  One of the advantages of this approach is that the array can be connected to other systems without needing to match the internal RAID controller card for the array to function properly.  While a single 300MB/s SATA channel will be sufficient for simpler compressed HD workflows on a budget, most professional arrays for high end editing systems will need more bandwidth than that, so most large eSATA arrays connect to the workstation with 1 or 2<a href="http://en.wikipedia.org/wiki/Serial_attached_SCSI#Connectors" target="_blank"> four channel</a> <a href="http://www.bhphotovideo.com/c/search?Ntt=SFF&amp;N=0&amp;BI=6727&amp;KBID=7302" target="_blank">cables</a>, using a variety of different physical interfaces depending on the vendor.</p>
<p>External <a href="http://www.bhphotovideo.com/c/search?Ntt=SAS+card&amp;N=0&amp;BI=6727&amp;KBID=7302" target="_blank">SAS</a> connected <a href="http://www.bhphotovideo.com/c/search?Ntt=SAS+array&amp;N=0&amp;BI=6727&amp;KBID=7302" target="_blank">arrays</a> function in much the same way as SATA based ones, but with a few advantages, that usually come at a significantly higher cost.  SAS is a full duplex interface, and the command set is based on SCSI instead of IDE, allowing higher performance and throughput.  More expensive SAS arrays also support multipath signaling, for greater redundancy in the supporting electronics. (As opposed to the redundancy provided at the disk level by RAID configurations)  SAS also supports much longer <a href="http://www.bhphotovideo.com/c/search?Ntt=SAS+cable&amp;N=0&amp;BI=6727&amp;KBID=7302" target="_blank">cable</a> lengths, up to 10 meters or 30 feet.  This can be advantagious for quiet video editing rooms, since the disk array, which is usually the loudest part of the system, can be located farther away from the users.</p>
<p>A number of vendors have now begun offering external arrays that interface with the host workstation via a direct extension of the <a href="http://www.bhphotovideo.com/c/search?Ntt=PCI+Express+TB&amp;N=0&amp;BI=6727&amp;KBID=7302" target="_blank">PCIe bus</a>.  This allows all of the RAID functionality to be contained within the array, and gives full speed access to the data as if it was contained within the machine.  Among the advantages of removing the RAID functionality from an internal add-on card, are that it can be attached to a laptop via an ExpressCard, which uses the same signaling protocol as PCIe, and that with addition of a few cheap <a href="http://www.bhphotovideo.com/c/product/534681-REG/CalDigit_731200_1_Port_PCI_Express_x4.html" target="_blank">pass-thru cards</a>, an array can easily be moved between systems.  This is definitely not a hot swappable solution, since it accesses the PCIe bus directly, which is initialized at bootup on most systems.  But if your main edit system has a total OS meltdown at a critical point in your project, it should be much easier to access your data from a different system than if you needed to reinstall the PCI SATA RAID card somewhere else, and allow you use your laptop as a backup edit system in certain instances.</p>
<p>Fibre Channel is by far the most expensive option.  Every part of the system is more expensive, the <a href="http://www.bhphotovideo.com/c/search?Ntt=Fibre+PCI&amp;N=0&amp;BI=6727&amp;KBID=7302" target="_blank">PCIe HBA cards</a>, the <a href="http://www.bhphotovideo.com/c/search?Ntt=Fibre+Cables&amp;N=0&amp;BI=6727&amp;KBID=7302" target="_blank">fiber cables</a>, and the <a href="http://www.bhphotovideo.com/c/search?Ntt=Fibre+Array&amp;N=0&amp;BI=6727&amp;KBID=7302" target="_blank">disk array controllers</a>.  On the otherhand, Fibre Channel offers capabilities that none of the other storage options really do.  It is a hot swappable interface, running on fiber cables that can extend access thousands of feet if desired, and can easily be networked and shared.  Devices can be connected directly together, shared in an <a href="http://en.wikipedia.org/wiki/Arbitrated_loop" target="_blank">Arbitrated Loop</a>, or all attached to a central fibre switch for simplified management.  It is an efficient and low latency interface, and is available in speeds of 1,2,4, or 8Gb per second, and multiple channels can be combined for higher performance.  Higher speed devices are usually backwards compatible with older hardware, similar to the way <a href="http://en.wikipedia.org/wiki/Ethernet" target="_blank">ethernet </a>works, allowing you to upgrade your storage network one piece at a time.</p>
<p>Choosing the right storage solution depends on your immediate media needs, your available budget, and the direction you anticipate growing in the future. SATA based solutions offer all of the speed you could need if scaled large enough.  SAS can offer similar performance in a smaller package, but at a higher cost.  Sharing data beyond gigabit network speeds requires a storage system that can interface with multiple computers, but that comes at a significantly increased initial cost.  Investing in Fibre Channel storage is usually only worth the expense if you anticipate the need to share your data on a SAN, either immediately or at some point in the future.  I will examine a few popular shared <a href="http://en.wikipedia.org/wiki/Storage_area_network" target="_blank">SAN</a> options in my next post.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.hd4pc.com/techblog/2010/12/05/post-production-media-storage-and-drive-arrays/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>New Workstation</title>
		<link>http://www.hd4pc.com/techblog/2008/01/22/new-workstation/</link>
		<comments>http://www.hd4pc.com/techblog/2008/01/22/new-workstation/#comments</comments>
		<pubDate>Tue, 22 Jan 2008 20:30:47 +0000</pubDate>
		<dc:creator>McCarthyTech</dc:creator>
				<category><![CDATA[Workflow Ideas]]></category>
		<category><![CDATA[Intel]]></category>
		<category><![CDATA[SAS]]></category>
		<category><![CDATA[SATA]]></category>
		<category><![CDATA[Xeon]]></category>

		<guid isPermaLink="false">http://www.hd4pc.com/techblog/2008/01/22/new-workstation/</guid>
		<description><![CDATA[After much searching and waiting, I finally got myself a new workstation to replace my Precision 670.  I now have a maxed out XW8400: Dual 3.0 Ghz 5365 Clovertown Intel Xeon Processors (8-Cores) 8GB Ram (Once I get a 64bit OS) QuadroFX 4600 Graphics Card (To power my 30&#8243; LCD) 2x300GB 15k RPM SAS Drives (125MB/s [...]]]></description>
			<content:encoded><![CDATA[<p>After much searching and waiting, I finally got myself a new workstation to replace my Precision 670.  I now have a maxed out <a target="_blank" href="http://h10010.www1.hp.com/wwpc/us/en/sm/WF25a/12454-12454-296719-307907-296721-1844968.html">XW8400</a>:</p>
<p>Dual 3.0 Ghz 5365 Clovertown Intel Xeon Processors (8-Cores)<br />
8GB Ram (Once I get a 64bit OS)<br />
<a target="_blank" href="http://www.nvidia.com/object/quadro_fx_5600_4600.html">QuadroFX 4600</a> Graphics Card (To power my 30&#8243; LCD)<br />
2x300GB 15k RPM SAS Drives (125MB/s each)</p>
<p>The XW8400 is currently one step behind the new top of the line <a target="_blank" href="http://h10010.www1.hp.com/wwpc/us/en/sm/WF25a/12454-12454-296719-307907-296721-3432827.html">XW8600</a>, but the <a target="_blank" href="http://en.wikipedia.org/wiki/PCI-X">PCI-X</a> slots, wider 3rd party support, and much lower price, weighted in its favor.  I will be doing some tests and benchmarks in the near future, so stay tuned for the results.  I am also curious to see if the Quadro4600 properly allows fullscreen overlay output in Prospect2K&#8217;s CineformRT Premiere mode, fixing the Geforce8 overlay problem.<br />
<span id="more-28"></span><br />
I got a ridiculously good deal on everything, since I waited nearly a year for the perfect opportunity, but I now have a few extra parts that I am not sure how to best utilize:</p>
<p>I already had all the disks I needed, with a 74GB 10k rpm SATA drive for OS and 4x 500GB SATA RAID5 for Data. My Raid5 is only getting 60-80MB/s with the integrated Intel Matrix storage controller, which is less than I was hoping for, but my data will be secure. If I continue to use the Raid5, I won&#8217;t have any place for my new, SAS drives worth $1000 bucks apiece. Alternately I could replace my Raid5 with a single 1TB disk for quantity storage with less security, and use the SAS disks in Raid0 for high-speed capture storage.</p>
<p>So that leaves me with a problem/question that I am looking for creative solutions to:<br />
I need a good external enclosure for either 2 SAS drives, or 4 SATA drives. With SAS, the key factor I would be looking for is speed, and with SATA, the key factor would be security. <a target="_blank" href="http://www.drobo.com/products_drobo.aspx">Drobo</a> comes to mind for the SATA drives, but is there a cheaper option with the same level of security, or better bandwidth?  Anyone know any good ways of externally connecting two SAS drives in Raid0?</p>
<p>Anyhow, export and render benchmark results to come, specifically with Premiere, AE, RedCine, and Cineform, plus a few FPS benchmarks for fun.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.hd4pc.com/techblog/2008/01/22/new-workstation/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Storage-Hard Drives</title>
		<link>http://www.hd4pc.com/techblog/2007/10/18/storage-hard-drives/</link>
		<comments>http://www.hd4pc.com/techblog/2007/10/18/storage-hard-drives/#comments</comments>
		<pubDate>Thu, 18 Oct 2007 07:56:15 +0000</pubDate>
		<dc:creator>McCarthyTech</dc:creator>
				<category><![CDATA[Industry Status]]></category>
		<category><![CDATA[Fibre Channel]]></category>
		<category><![CDATA[SAS]]></category>
		<category><![CDATA[SATA]]></category>

		<guid isPermaLink="false">http://www.hd4pc.com/techblog/2007/10/18/storage-hard-drives/</guid>
		<description><![CDATA[There are many different issues that need to be taken into consideration when evaluating data storage options for post-production.  Cost is a primary factor to consider, since without that issue, there would be little to weight against high end systems.  Performance is key as well, for efficiency as well as creativity.  Reliability is a frequently undervalued [...]]]></description>
			<content:encoded><![CDATA[<p>There are many different issues that need to be taken into consideration when evaluating data storage options for post-production.  Cost is a primary factor to consider, since without that issue, there would be little to weight against high end systems.  Performance is key as well, for efficiency as well as creativity.  Reliability is a frequently undervalued consideration, that effects everything from insurance prices to stress levels.  The ability to share data effectively can be an important consideration, since post-production is usually a collabrative effort.</p>
<p>The industry has responded with many different solutions, that vary in concept beyond recognition and in price by many orders of magnitude.  The earliest solutions involved video tape, analog replaced by digital recording.  Hard disks were introduced for random access to data, and now those are slowly beginning to be replaced by solid state flash chips.  Since this site is targeted to PC users, we will focus on hard disk based solutions, and the interfaces with which they can be accessed by a media workstation.</p>
<p>Hard disks are produced with five popular interfaces:  IDE/ATAPI, Serial-ATA (SATA), Small Computer System Interface (SCSI), Serial Attached SCSI (SAS), and Fibre Channel (FC).  IDE and SCSI interfaces are currently being phased out and replaced by their more capable and flexible Serial varients.  I know little of true Fibre Channel hard disks, but that format is rarely used in this industry.  That leaves only two options, which are now somewhat similar and compatible, SATA and SAS.  With identical connection cables, and both offered in 3.5&#8243; and 2.5&#8243; form factors, it is hard to tell the two options apart visually.  Their interfaces both support 300MB/s, dedicated buses for each drive, and port splitting when that is not required.<br />
<span id="more-13"></span><br />
The biggest differences between SATA and SAS are performance and cost, which eventually distill down to one issue: size.  SAS disks have slightly more capable and efficient electronics, run fewer platter, with less data, and much higher RPMs and faster I/O and transfer rates.  SATA drives usually have much more storage capacity, lower speeds, and are always much cheaper.  At first glance, high end post production work would seem suited for SAS drives, since moving picture footage requires a higher data transfer rate than almost any other application of computing technology.</p>
<p>There are four other factors, which when combined, weight much more heavily in favor of SATA.  The first is price.  Since the difference in price per Gigabyte is currently so great, and SATA drives are not that different in their design or performance, a few quick calculations will reveal that while SAS disks have higher performance per drive, SATA disks deliver more performance per dollar, regardless of their storage capacity.  Second is that the infrastructure needed to aggregate the performance of multiple disks (Raid arrays) will be required, regardless of which disk solution we choose.  This is due to the fact that HD resolutions and larger require much higher data transfer rates than any single drive can provide (unless compressed, and even then, fast disk access is beneficial).  The marginal cost to increase the number of drives being aggregated will be low in many cases.  The third factor is that digitalized footage requires a tremendous amount of storage space, once again contributing to the need for many hard drives to be combined.  Lastly, most of the popular solutions to improve reliability, do so by utilizing even more capacity, to store redundant information in the form of parity, or straight backups.</p>
<p>These factors, when combined make a strong case for SATA disks, which have higher capacity at the expense of performance per drive.  If we are combining drives anyway, the performance benefits of SAS will usually be negated by combining more SATA drives for less money.  This is a case where quantity can clearly overcome quality in most instances.  As a side benefit, SATA drives usually have much greater capacities.</p>
<p>The only time when SAS may be favorable, will be when there is little need for high capacity, and when there is value to smaller solutions.  Fewer SAS disks are required to reach a given level of performance, and will therefore be more portable, require less power, and frequently generate less heat and noise.  For visual effects, were a few seconds of footage are manipulated at very high quality, or short commercials, SAS may be a more efficient option.</p>
<p>In most cases though, the numbers come down in favor of SATA by along shot.  Let&#8217;s imagine a two hour movie, with a 10:1 shooting ratio, giving us 20 hours of footage, and for the sake of example, let&#8217;s assume a data rate of 100MB/s.  With 3600 seconds in an hour, that is 360000MB an hour, or 360GB.  20 hours of footage would require 7.2TB of storage.  Add 10% to avoid disk fragmentation, and you need an 8TB array.  With 1TB SATA disks you need 8, plus two more to support Raid 50.  You will have the bandwidth of eight drives, and assuming 50MB/s each for SATA disks, and an efficient controller interface, that is 400 MB/s, more than enough for our 100MB/s files.  10 SATA drives at 1TB currently costs ago $3,000, and the Raid hardware will be required by both SATA and SAS, so it does not necessarily need to be factored in.  Now when onlining a production, not all footage is usually captured, but when you factor in captures, conformed exports, film and video colored versions, testless and texted masters, a 10:1 ratio will not be an inaccurate estimate.  Now I used round numbers, so that if the datarate of your format of choice is higher or lower, you can ajust accordingly. 200MB/s footage would need 20 disks, but could get double performance.  50MB/s footage would only need 5 disks, but could still expect 200MB/s of performance.  Have less footage, I left a 4x overhead in this example with 20 hours of source, but I also used 1TB drives for my calculations.  With 10 hours, 500GB drives show SATA to be even more economically favorable.</p>
<p>Now for a quick comparison to SAS, we start by noting that the maximum capacity is 300GB, and you can expect to pay at least $500 per disk.  Our 8TB example would require about thirty disks, assuming a Raid 50, striping together three Raid 5 arrays of ten disks. 27 data disks is 8.1TB for a cost of $15,000 in drives alone, not counting that it requires hardware for three 10 bay array enclosures instead of one.  From a performance perspective, assuming 80MB/s per disk, you can get over 2GB/s if you want to pay for an interface that fast, but remember that this is all for footage that is 100MB/s.  2GB/s might be good if you want to share it between multiple systems, but with that many users, usually multiple productions will be processed concurrently, requiring much more storage capacity anyway.  By multiplying up and down for different formats, it becomes clear that there is no way that SAS can economically catch up.</p>
<p>So I hope this successfully establishes that SATA disk drives will almost always be the drive type of choice for post-production environments.  I plan to examine the different options for connecting these drive arrays to a workstation or group of systems in my next post.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.hd4pc.com/techblog/2007/10/18/storage-hard-drives/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

