Avid ISIS 7000 v2.3 Performance and Redistribution Guide

Transcription

1 Avid ISIS 7000 v2.3 Performance and Redistribution Guide Change History Date Revised 1/27/2011 v2.3 Release 9/16/2010 v2.2.2 Changes Made Avid ISIS 7000 v2.3 provides higher bandwidth on RAID Storage Groups with the latest release of Avid editing systems. The RAID Storage Group read rating has gone from 350 MB/s to 400 MB/s and the write rating from 160 MB/s to 200 MB/s, see Engine Bandwidth Performance Ratings (MB/s) with Avid Devices on Page 218. Avid has lifted the restriction on requiring a separate Storage Group for Apple Final Cut Pro media in the Avid ISIS 7000 v2.2.2 shared storage environment, see Supported Stream Counts with Apple Final Cut Pro on Page 18. 6/7/2010 v2.2 2/5/2010 v2.1.1 Avid ISIS v2.2 adds support for Windows 7 clients. This revision adds data for RGB resolutions and Macintosh ultra high resolution clients (UHRC). Avid has completed its characterization of Apple Final Cut Pro on RIAD Storage Groups in an Avid ISIS v2.1.1 shared storage environment, see Supported Stream Counts with Apple Final Cut Pro on Page 18. Executive Summary This document provides performance guidance for Avid ISIS v2.1.1 through v2.3 releases. These releases support RAID6. Updated charts and examples have been provided to give guidance under normal as well as redistribution conditions. Contents Engine and Switch Performance... 2 Engine Bandwidth Performance Ratings (MB/s) with Avid Devices... 2 Examples of How to Apply Engine Ratings... 3 Switch Performance... 4 RAID6 Performance Guidance During Storage Element Failures... 5 Supported Stream Counts with Avid Editors... 6 Supported Stream Counts with Avid Non-Editor Capture Devices Supported Stream Counts with Avid Non-Editor Playback Devices Redistribution and Performance for Mirrored and RAID Single Blade Removal Redistribution for Mirrored Storage Groups Single Blade Removal Redistribution for RAID6 Storage Groups Single Blade Add Redistribution Mirrored Storage Groups Adding a Single or Multiple Engines to a Mirrored Storage Group Single Blade Add Redistribution for RAID6 Storage Groups Symmetric Redistributions on Storage Groups Non-Symmetric Full Redistribution for Mirrored Storage Groups Non-Symmetric Full Redistribution for RAID6 Storage Groups... 18

2 Supported Stream Counts with Apple Final Cut Pro Hardware and Software Used During Testing Improved Performance Capabilities for ISIS v2.2.x Support for RAID6 Storage Groups Performance guidance during storage element failure with RAID6 Additional streams counts for mirrored Storage Groups Performance guidance for Avid AirSpeed and AirSpeed Multi Stream devices Macintosh 10 Gb Ethernet UHRC support Windows 7 client support Capturing with Windows clients using Nitris DX and Mojo DX to RAID6 workspaces have been qualified Engine and Switch Performance Avid ISIS scales in a linear fashion and is based on the amount of bandwidth an ISIS engine (or several engines) are able to provide. The following table defines an engine s capabilities based on the chunk size, protection type and switch type in use. A mix of Avid editors and test tools in Zone 1, 2 and 3 were used to generate bandwidth on the system during testing. Engine Bandwidth Performance Ratings (MB/s) with Avid Devices To determine the available bandwidth for mirrored Storage Groups when utilizing a mix of readers and writers be sure to multiply the write rate x2. The results should then be subtracted from the Read engine rating. To determine the available bandwidth for RAID6 Storage Groups when utilizing a mix of readers and writers be sure to multiply the write rate x2.2. The results should then be subtracted from the Read engine rating. Exceeding 90% capacity will reduce the available bandwidth by 15%. Block Size 256 Chunk Size 512 Chunk Size Mirrored Mirrored RAID6 Switch ISS1000 or ISS2000 ISS2000 Storage Blade SD Writes SD Reads HD/SD Writes HD/SD Reads Writes Reads Writes Reads i2000 N/S N/S N/S N/S I I

3 Examples of How to Apply Engine Ratings Example 1: Single engine using a mirrored Storage Group with a mix of capture and playback devices # of Client Protection Chunk Format/ Data Rate Switch # of Streams Clients Type Type Size per Stream Bandwidth 1 10 Gb Mirrored 512 KB ISS i / 8Bit HD 2 (reader) 125 MB/s 250 MB/s 2 1 Gb Mirrored 512 KB ISS i /720p DNxHD220 2 (reader 28 MB/s 112 MB/s 2 1 Gb Mirrored 512 KB ISS i / DV50 1 (writes) 8 MB/s 32 MB/s Total Bandwidth Required = 394 MB/s Passed: In this example the total throughput required would fall in line with the read engine rating of 400 MB/s used when mixing capture and playback devices. Note: Captures to a mirrored Storage Group are 2X when mixing with playback clients. Example 2: Single engine using a mirrored Storage Group with a mix of capture and playback devices # of Clients Client Type Protection Type Chunk Size Switch 1 10 Gb Mirrored 512 KB ISS Gb Mirrored 512 KB ISS Gb Mirrored 512 KB ISS2000 Format/ 1080i / 10Bit HD 1080i DNxHD i DNxHD220 # of Streams Data Rate per Stream Bandwidth 2 (reader) 150 MB/s 300 MB/s 2 (reader) 28 MB/s 56 MB/s 1 (writer) 28 MB/s 56 MB/s Total Bandwidth Required = 412 MB/s Failed: In this example the total throughput required would not fall in line with the read engine rating of 400 MB/s. Note: Captures to a mirrored Storage Group are 2X when mixing with playback clients. Example 3: Single engine using a RAID6 Storage Group with only capture devices # of Client Protection Chunk Format/ # of Data Rate Switch Clients Type Type Size Streams per Stream Bandwidth 3 ASMS RAID6 512 KB ISS i XDCAM50 Mb 4 (writer) 10 MB/s 120 MB/s 1 ASMS RAID6 512 KB ISS i / DV50 2 (writer) 10 MB/s 20 MB/s 2 ASC RAID6 512 KB ISS i / DV50 1 (writer) 10 MB/s 20 MB/s Total Bandwidth Required = 160 MB/s Passed: The total throughput required would fall in line with the write engine rating of 200 MB/s. Note: This was 100% capture devices. 3

4 Example 4: Single engine using a RAID6 Storage Group with a mix of capture and playback devices # of Client Protection Chunk Format/ # of Data Rate Switch Clients Type Type Size Streams per Stream Bandwidth 3 ASMS RAID6 512 KB ISS i XDCAM50 Mb 4 (reader) 10 MB/s 120 MB/s 2 ASC RAID6 512 KB ISS i / DV50 1 (reader) 10 MB/s 20 MB/s 2 ASMS RAID6 512 KB ISS i XDCAM50 Mb 4 (writer) 10 MB/s 176 MB/s 1 ASMS RAID6 512 KB ISS i / DV50 1 (writer) 10 MB/s 22 MB/s Total Bandwidth Required = 338 MB/s Passed: The total throughput required would fall in line with the read engine rating of 400 MB/s used when mixing capture and playback devices. Note: Captures to a mirrored Storage Group are 2X when mixing with playback clients. o ASMS = AirSpeed Multi Stream o ASC = AirSpeed Classic Switch Performance The performance for Avid ISIS clients and servers is based on the generation of the switch hardware (ISS and IXS) in the engine and the Chunk Size. The following gives you a base number of the MB/s you can expect of each generation. Avid ISIS Switch Performance (MB/s) Block Size 256 Chunk Size 512 Chunk Size Switch ISS1000 ISS2000 ISS1000 ISS2000 Bandwidth N/S 600 Note: These ratings can be attained by using 10 Gb, 1 Gb, or a combination of both. Example of How to Apply Switch Ratings to a Mirrored Storage Group # of Clients Client Speed Size of trunk Chunk Size Format Switch Bandwidth Pass / Fail 4 10 Gb 20 Gb 1:1 10Bit HD 512 KB 1080i ISS MB/s Pass 5 10 Gb 20 Gb 1:1 10Bit HD 512 KB 1080i ISS MB/s Fail 10 1 Gb 10 Gb DNxHD KB 1080i ISS MB/s Pass 11 1 Gb 10 Gb DNxHD KB 1080i ISS MB/s Fail 40 1 Gb 40 Gb DNxHD KB 1080i ISS MB/s Pass Note: A Cisco 4900M was the Zone 2 and 3 switch used during testing. All bandwidth is based on reading 2 streams of video and 8 audio tracks. 4

5 Example of How to Apply Switch Ratings to a RAID6 Storage Group # of Clients Client Speed Size of trunk Chunk Size Format Switch Bandwidth Pass / Fail 22 1 Gb 20 Gb XDCAM50 Mb 512 KB 1080i ISS MB/s Pass 76 1 Gb 20 Gb XDCAM50 Mb 512 KB 1080i ISS MB/s Fail 40 1 Gb 10 Gb DV KB 30i ISS MB/s Pass 45 1 Gb 10 Gb DV KB 30i ISS MB/s Fail Note: Note: Writes to a RAID6 Storage Group should be multiplied x2.2. A Cisco 4900M was the Zone 2 and 3 switch used during testing. All bandwidth is based on reading 2 streams of video and 8 audio tracks. RAID6 Performance Guidance During Storage Element Failures One of the advantages of RAID6 is the ability to continue working during the event of storage element failure. Should this event occur your engine rating is degraded by 30% of its normal operation. See the redistribution section for the amount of bandwidth that can be sustained during the recovery process. The following are examples of how to apply engine ratings during a Storage Element failure. Example 1: Single engine using a RAID6 Storage Group with capture devices only # of Clients Client Type Protection Type Chunk Size Switch # of Streams Data Rate per Stream Bandwidth 2 ASMS RAID6 512 KB ISS2000 DV50 2 (writer) 10 MB/s 40 MB/s 2 ASC RAID6 512 KB ISS2000 DV50 1 (writer) 10 MB/s 20 MB/s Total Bandwidth Required = 60 MB/s Passed: The total throughput required would fall in line with the degraded write engine rating which would now be 140 MB/s in this state (70% of 200 MB/s). Note: This was 100% capture devices. Example 2: Two engines using a RAID6 Storage Group with only capture devices # of Clients Client Type Protection Type Chunk Size Switch Format/ # of Streams Data Rate per Stream Bandwidth 1 ASC RAID6 512 KB ISS2000 DV50 1 (reader) 10 MB/s 10 MB/s 3 ASMS RAID6 512 KB ISS2000 XDCAM50 Mb 4 (writer) 10 MB/s 264 MB/s 1 ASMS RAID6 512 KB ISS2000 DV50 3 (writer) 10 MB/s 66 MB/s Total Bandwidth Required = 340 MB/s Passed: The total throughput required would fall in line with the degraded engine rating of a two engine Storage Group which would now be 560 MB/s in this state (70% of 800 MB/s). Note: Capture to a RAID6 Storage Group is 2.2X when mixing with playback clients. o ASMS = AirSpeed Multi Stream o ASC = AirSpeed Classic 5

6 Supported Stream Counts with Avid Editors The charts in this section define the bandwidth used per resolution and a recommended stream count. Take the following into consideration when reading the tables below. Avid stresses that the information in the following charts is based on the Avid ISIS v2.x default file system chunk size of 512 KB. When using a 256 KB File system please refer to the ISIS v1.5 Performance guide, search the Avid Knowledge Base at for the Avid ISIS 7000 Performance Guide. All bandwidth ratings have been adjusted to include up to 8 tracks of 16 bit 48 KHz. For supported application revisions, see the Avid ISIS 7000 v2.x ReadMe. The sequences used in Avid testing have two second audio and video cuts offset by one second. RAID6 Storage Groups only support resolutions of 50 Mb and below. For some platforms, achieving the highest stream count may require switching the video quality mode during playback operations. (e.g. Draft or Full Quality). 10-bit RGB is limited to single stream in 1080 formats only and requires the use of Media Composer 5.0, Symphony 5.0 or NewsCutter bit RGB playback and capture is supported on 64-Bit operating systems only. The results in the following charts were achieved using the platforms and editors listed in (see Hardware and Software Used During Testing on page 21). Stream counts vary depending on the platform and editor version. You might be able to achieve higher stream counts on the newer platforms." DV Project Number of Streams per client (MB/s) Multi-cam (MB/s) Format way 9-way GB/Hour DV 25 30i NTSC PAL DV 50 30i NTSC PAL N/S o Shaded cells indicate 10 Gb connectivity required (UHRC) not supported during a redistribution. MPEG Project Number of Streams per client (MB/s) Multi-cam (MB/s) Format way 9-way GB/Hour MPEG 30 30i NTSC MPEG 40 30i NTSC MPEG 50 30i NTSC o Shaded cells indicate 10 Gb connectivity required (UHRC) not supported during a redistribution. 6

7 JFIF Progressive Project Number of Streams per client (MB/s) Multi-cam (MB/s) Format way 9-way GB/Hour 35:1 24p p NTSC p, 24p PAL :1 24p, p NTSC p, 24p PAL :1 24p, p NTSC p, 24p PAL :1 24p, p NTSC p, 24p PAL :1 SD 24p, p NTSC N/S p, 24p PAL N/S :1 SD 24p, p NTSC N/S N/S p, 24p PAL N/S N/S :1 10b SD 24p, p NTSC N/S N/S p, 24p PAL N/S N/S VC1-APL0 25p N/S N/S N/S 2.7 VC1-APL1 25p N/S N/S N/S 5.5 o Shaded cells indicate 10 Gb connectivity required (UHRC) not supported during a redistribution. JFIF Interlaced 15:1s 4:1s 2:1s 20:1 10:1 3:1 2:1 1:1 SD 1:1 10b SD Project Format Number of Streams per client (MB/s) Multi-cam (MB/s) way 9-way GB/Hour N/S N/S N/S N/S N/S

8 VC1-APL0 24, , N/S N/S N/S 2.7 VC1-APL1 24, , N/S N/S N/S 5.5 VC1-APL2 24, , N/S N/S N/S 11 o Shaded cells indicate 10 Gb connectivity required (UHRC) not supported during a redistribution. 1080i Project Number of Streams per client (MB/s) Multi-cam (MB/s) Format way 9-way GB/Hour RGB 10-bit * 240 N/S N/S N/S N/S N/S 864 1:1 10-bit HD N/S N/S N/S N/S 527 1:1 HD N/S N/S N/S 439 DNxHD 220 X N/S DNxHD N/S DNxHD N/S XDCAM N/S N/S 40 N/S i/59.94 XDCAM N/S N/S 25 N/S 18 XDCAM N/S N/S 17.5 N/S 13 XDCAM N/S N/S 12.5 N/S 9 DVCPRO HD N/S AVC-Intra N/S N/S N/S N/S 28 AVC-Intra N/S N/S N/S N/S 50 VC1-APL N/S N/S N/S 21 RGB 10-bit * 206 N/S N/S N/S N/S N/S 742 1:1 10-bit HD N/S N/S N/S N/S 461 1:1 HD N/S N/S N/S 369 DNxHD 185 X N/S DNxHD N/S DNxHD N/S DVCPRO HD N/S i 50 XDCAM N/S N/S 40 N/S 28 XDCAM N/S N/S 25 N/S 18 XDCAM N/S N/S 17.5 N/S 13 XDCAM N/S N/S 12.5 N/S 9 AVC-Intra N/S N/S N/S N/S 28 AVC-Intra N/S N/S N/S N/S 50 VC1-APL N/S N/S N/S 21 o Shaded cells indicate 10 Gb connectivity required (UHRC) not supported during a redistribution. o * One stream of video and 8 tracks of audio are supported. 8

9 1080p Project Format Number of Streams per client (MB/s) Multi-cam (MB/s) way 9-way GB/Hour RGB 10-bit * 240 N/S N/S N/S N/S N/S 864 1:1 10-bit HD N/S N/S N/S N/S 527 1:1 HD N/S N/S N/S 439 DNxHD 220 X N/S DNxHD N/S p/29.97 DNxHD N/S XDCAM N/S N/S 40 N/S 28 XDCAM N/S N/S 25 N/S 18 XDCAM N/S N/S 17.5 N/S 13 DNxHD RGB 10-bit * 206 N/S N/S N/S N/S N/S 742 1:1 10-bit HD N/S N/S N/S N/S 461 1:1 HD N/S N/S N/S 373 DNxHD 185 X N/S DNxHD N/S DNxHD p/ N/S XDCAM N/S N/S 40 N/S 28 XDCAM N/S N/S 25 N/S 18 XDCAM N/S N/S 17.5 N/S 13 DNxHD VC1-APL N/S N/S N/S 4 RGB 10-bit * 196 N/S N/S N/S N/S N/S 706 1:1 10-bit HD N/S N/S N/S N/S 443 1:1 HD N/S N/S N/S 355 DNxHD 175 X N/S DNxHD N/S DNxHD p/ N/S XDCAM N/S N/S 25 N/S 18 XDCAM N/S N/S 17.5 N/S 13 XDCAM N/S N/S 12.5 N/S 9 DNxHD VC1-APL N/S N/S N/S 21 RGB 10-bit * 196 N/S N/S N/S N/S N/S 706 1:1 10Bit HD N/S N/S N/S N/S 527 1:1 HD N/S N/S N/S 355 DNxHD 175 X N/S DNxHD N/S DNxHD N/S XDCAM p/ N/S N/S 25 N/S 18 XDCAM N/S N/S 17.5 N/S 13 XDCAM N/S N/S 12.5 N/S 9 DNxHD AVC-Intra N/S N/S N/S N/S 28 AVC-Intra N/S N/S N/S N/S 50 VC1-APL N/S N/S N/S 21 o Shaded cells indicate 10 Gb connectivity required (UHRC) not supported during a redistribution. o * One stream of video and 8 tracks of audio are supported. 9

10 720p Project Format Number of Streams per client (MB/s) Multi-cam (MB/s) way 9-way GB/Hour 1:1 10-bit HD N/S N/S N/S N/S 499 1:1 HD N/S N/S N/S 373 DNxHD 220 X N/S DNxHD N/S DNxHD N/S XDCAM N/S N/S 40 N/S p/59.94 XDCAM N/S N/S 25 N/S 18 XDCAM N/S N/S 17.5 N/S 13 DVCPRO HD N/S AVC-Intra N/S N/S N/S N/S 28 AVC-Intra N/S N/S N/S N/S 50 VC1-APL N/S N/S N/S 11 1:1 10-bit HD N/S N/S N/S N/S 422 1:1 HD N/S N/S N/S 313 DNxHD 185 X N/S DNxHD N/S DNxHD N/S XDCAM N/S N/S 40 N/S p/50 XDCAM N/S N/S 25 N/S 18 XDCAM N/S N/S 17.5 N/S 13 DVCPRO HD 8 16 N/S N/S 40 N/S 28 AVC-Intra N/S N/S N/S N/S 28 AVC-Intra N/S N/S N/S N/S 50 VC1-APL N/S N/S N/S 11 1:1 10-bit HD N/S N/S N/S N/S 250 1:1 HD N/S N/S N/S 186 DNxHD 220 X N/S p/29.97 DNxHD N/S DNxHD N/S DVCPRO HD N/S :1 10-bit HD N/S N/S N/S N/S 211 1:1 HD N/S N/S N/S 169 DNxHD 90 X N/S DNxHD N/S DNxHD p/ N/S XDCAM N/S N/S 25 N/S 18 XDCAM N/S N/S 17.5 N/S 13 AVC-Intra N/S N/S N/S N/S 28 AVC-Intra N/S N/S N/S N/S 50 1:1 10-bit HD N/S N/S N/S N/S 204 1:1 HD N/S N/S N/S 162 DNxHD 90 X N/S DNxHD N/S DNxHD N/S XDCAM35 720p/ N/S N/S 25 N/S 18 XDCAM N/S N/S 17.5 N/S 13 DVCPRO HD N/S AVC-Intra N/S N/S N/S N/S 28 AVC-Intra N/S N/S N/S N/S 50 VC1-APL N/S N/S N/S 11 o Shaded cells indicate 10 Gb connectivity required (UHRC) not supported during a redistribution. 10

11 Supported Stream Counts with Avid Non-Editor Capture Devices The following charts outline Avid supported capture devices and stream counts. The GB/Hour column represents the use of a single stream. Device Project Format Note: Bandwidth limiting might be required to ensure the above ratings. Number of Streams per Client (MB/s) GB/Hour per Stream XDCAM-HD 17.5 Mb AirSpeed Multi Steam 1080i XDCAM-HD 35 Mb AirSpeed Multi Steam 1080i XDCAM-HD 50 Mb AirSpeed Multi Steam 1080i HDV 25 Mb AirSpeed Multi Steam 1080i DV50 AirSpeed Multi Steam 1080i DV25 AirSpeed Multi Steam 1080i IMX50 AirSpeed Multi Steam 30i NTSC N/S N/S 36 IMX30 AirSpeed Multi Steam 30i NTSC N/S N/S 22 DV25 AirSpeed Classic 30i NTSC N/S N/S 22 DV50 AirSpeed Classic 30i NTSC N/S N/S 36 IMX50 AirSpeed Classic 30i NTSC N/S N/S 36 IMX30 AirSpeed Classic 30i NTSC N/S N/S 22 DNxHD115 AirSpeed Classic 1080i N/S N/S N/S 64 DNxHD120 AirSpeed Classic 1080i N/S N/S N/S 64 DNxHD145 AirSpeed Classic 1080i N/S N/S N/S 78 SD 1:1 AirSpeed Classic 30i NTSC 25 N/S N/S N/S 88 MPEG-2 Avid Low-Res Encoder 30i NTSC MPEG-4 Avid Low-Res Encoder 30i NTSC 200 kb 400 kb 600 kb 800 kb 1 DNxHD145 AirSpeed Multi Steam 1080i N/S N/S 72 DNxHD220 AirSpeed Multi Steam 1080i N/S N/S N/S

12 Supported Stream Counts with Avid Non-Editor Playback Devices The following table outlines Avid supported playback devices and stream counts. Device Project Format Number of Streams per client (MB/s) XDCAM-HD 17.5 Mb AirSpeed Multi Steam 1080i XDCAM-HD 35 Mb AirSpeed Multi Steam 1080i XDCAM-HD 50 Mb AirSpeed Multi Steam 1080i DNxHD145 AirSpeed Multi Steam 1080i N/S N/S DNxHD220 AirSpeed Multi Steam 1080i N/S N/S N/S HDV 25 Mb AirSpeed Multi Steam 1080i DV50 AirSpeed Multi Steam 1080i DV25 AirSpeed Multi Steam 1080i IMX50 AirSpeed Multi Steam 30i NTSC IMX30 AirSpeed Multi Steam 30i NTSC DV25 AirSpeed Classic 30i NTSC 6 12 N/A N/A DV50 AirSpeed Classic 30i NTSC N/A N/A IMX50 AirSpeed Classic 30i NTSC N/A N/A IMX30 AirSpeed Classic 30i NTSC 6 12 N/A N/A DNxHD115 AirSpeed Classic 1080i N/A N/A DNxHD120 AirSpeed Classic 1080i N/A N/A DNxHD145 AirSpeed Classic 1080i N/A N/A SD 1:1 AirSpeed Classic 30i NTSC N/A N/A Note: Bandwidth limiting might be required to ensure the above ratings. 12

13 Redistribution and Performance for Mirrored and RAID6 The following sections helps you understand the amount of bandwidth that can be sustained during redistribution and the time to completion based on the used capacity of a given configuration. Take the following into consideration when reading the following tables. Use 1 Gb resolution guidelines for UHRC clients during Redistribution. Nitris and Mojo DX attached editors might require a stream reduction during redistribution. Single Blade Removal Redistribution for Mirrored Storage Groups Use the following tables to determine the amount of time required when removing a single ISB from an existing mirrored Storage Group. The tables are based on the bandwidth to the Storage Group and the amount of data that will be removed from the ISIS Storage Blade (ISB). Time to Completion with No Bandwidth (Hours) Storage Blade i1000 i2000 i1000 i2000 i1000 i2000 i1000 i2000 i1000 i2000 i1000 i Engine.75 N/S N/S N/S Engines.5 N/S N/S N/S Engines.25 N/S N/S N/S.5 1 Time to Completion with 120 MB/s of Client Bandwidth per Engine (Hours) Storage Blade i1000 i2000 i1000 i2000 i1000 i2000 i1000 i2000 i1000 i2000 i1000 i Engine 1 N/S N/S N/S Engines.5 N/S N/S N/S Engines.25 N/S N/S N/S Time to Completion with 200 MB/s of Client Bandwidth per Engine (Hours) Storage Blade i1000 i2000 i1000 i2000 i1000 i2000 i1000 i2000 i1000 i2000 i1000 i Engine N/S N/S N/S N/S N/S N/S N/S N/S N/S N/S N/S N/S 6 Engines 1 N/S N/S N/S Engines 1 N/S N/S N/S

14 Single Blade Removal Redistribution for RAID6 Storage Groups Use the following tables to determine the amount of time required when removing a single ISB from an existing RAID6 Storage Group. The tables are based on the bandwidth to the Storage Group and the amount of data that will be removed from the ISIS Storage Blade (ISB). Time to Completion with No Bandwidth (Hours) Storage Blade i1000 i2000 i1000 i2000 i1000 i2000 i1000 i2000 i1000 i2000 i1000 i Engine N/S N/S N/S N/S N/S N/S Engines N/S N/S 1 2 N/S N/S 2 4 N/S N/S Engines N/S N/S.5.75 N/S N/S N/S N/S 2 3 Time to Completion with 150 MB/s of Client Bandwidth per Engine (Hours) Storage Blade i1000 i2000 i1000 i2000 i1000 i2000 i1000 i2000 i1000 i2000 i1000 i Engine N/S N/S N/S N/S 5 10 N/S N/S Engines N/S N/S 2 4 N/S N/S 4 8 N/S N/S Engines N/S N/S N/S N/S 3 6 N/S N/S 5 10 Single Blade Add Redistribution Mirrored Storage Groups Use the following table to determine the amount of time required when adding a single ISB to an existing Storage Group. The table is based on the bandwidth to the Storage Group, as well as the amount of data being added to the ISIS Storage Blade (ISB). Time to Completion (Hours) 1-12 Engines Storage Blade i1000 i2000 i1000 i2000 i1000 i2000 i1000 i2000 i1000 i2000 i1000 i2000 No Bandwidth 3 N/S N/S N/S MB/s of B/W 4 N/S N/S N/S MB/s of B/W 6 N/S N/S N/S

15 Adding a Single or Multiple Engines to a Mirrored Storage Group Use the following tables to determine the amount of time required when adding a single or multiple engines to an existing Storage Group. The tables are based on the bandwidth to the Storage Group, as well as the amount of data being added. Time to Completion with no Bandwidth (Hours) Storage Blade i1000 i2000 i1000 i2000 i1000 i2000 i1000 i2000 i1000 i2000 i1000 i Engines 2.4 N/S N/S N/S Engines 3.2 N/S N/S N/S Engines 3.6 N/S N/S N/S Engines 3.8 N/S N/S N/S Engines 4 N/S N/S N/S Engines 4 N/S N/S N/S Engines 4 N/S N/S N/S Engines 4 N/S N/S N/S Engines 4 N/S N/S N/S Engines 4 N/S N/S N/S Engines 4 N/S N/S N/S 9 18 Time to Completion with 120 MB/s of Client Bandwidth per Engine (Hours) Storage Blade i1000 i2000 i1000 i2000 i1000 i2000 i1000 i2000 i1000 i2000 i1000 i Engines 5 N/S N/S N/S Engines 6.5 N/S N/S N/S Engines 7 N/S N/S N/S Engines 7.5 N/S N/S N/S Engines 8 N/S N/S N/S Engines 8 N/S N/S N/S Engines 8 N/S N/S N/S Engines 7.5 N/S N/S N/S Engines 7.5 N/S N/S N/S Engines 8 N/S N/S N/S Engines 8 N/S N/S N/S

16 Single Blade Add Redistribution for RAID6 Storage Groups Use the following table to determine the amount of time required when adding a single ISB to an existing Storage Group. The table is based on the bandwidth to the Storage Group, as well as the amount of data being added to the ISIS Storage Blade (ISB). Time to Completion (Hours) 1-12 Engines Storage Blade i1000 i2000 i1000 i2000 i1000 i2000 i1000 i2000 i1000 i2000 i1000 i2000 No Bandwidth N/S N/S 3 6 N/S N/S 6 12 N/S N/S MB/s of B/W N/S N/S 5 10 N/S N/S N/S N/S Symmetric Redistributions on Storage Groups For the ISIS 2.x release dramatic improvements had been made for the time a full redistribution takes to complete. Some full redistributions that formerly took multiple hours can now be completed in a 20 minutes to 2 hours depending on your protection type. To experience the benefits of these faster full redistributions there are two requirements. First, all workspaces in the Storage Group must participate in the full redistribution. Second, ISB adds and removals must be done in a symmetric fashion leading up to the full redistribution. This means that the same quantity of ISBs that were removed from a Storage Group need to then be added in a single configuration change. The following examples explain how this works. Example 1: 1) Remove a single ISB from the Storage Group. 2) Then add a single ISB to the same Storage Group. 3) Perform a Full redistribution to all workspaces in the Storage Group. Example 2: Total time to completion should be less than 20 minutes. 1) Remove a single ISB from the Storage Group. 2) Remove two ISBs from the Storage Group. 3) Add three ISBs back to the Storage Group in a single configuration change. 4) Perform a Full redistribution to all workspaces in the Storage Group. Example 3: Total time to completion should be less than 20 minutes. 1) Remove two ISBs from the Storage Group. 2) Add one ISB back to the Storage Group in a single configuration change. 16

17 3) Add one ISB back to the Storage Group in a single configuration change. 4) Perform a Full redistribution to all workspaces in the Storage Group. This example would not qualify for a quick redistribution like the two previous examples because all the ISBs previously removed were not added back in a single configuration change. For nonsymmetrical full redistribution guidance, refer to the following tables. Non-Symmetric Full Redistribution for Mirrored Storage Groups The following tables should help you estimate the full redistribution times with non-symmetric configuration changes when using a mirrored workspace. Time to Completion with No Bandwidth (Hours) Storage Blade i1000 i2000 i1000 I2000 i1000 i2000 i1000 i2000 i1000 i2000 i1000 i Engine 6.0 N/S N/S N/S Engines 4.7 N/S N/S N/S Engines 3.9 N/S N/S N/S Time to Completion with 120 MB/s of Client Bandwidth per Engine (Hours) Storage Blade i1000 i2000 i1000 I2000 i1000 i2000 i1000 i2000 i1000 i2000 i1000 i Engine 6.7 N/S N/S N/S Engines 5.0 N/S N/S N/S Engines 4.2 N/S N/S N/S Time to Completion with 200 MB/s of Client Bandwidth per Engine (Hours) Storage Blade i1000 i2000 i1000 I2000 i1000 i2000 i1000 i2000 i1000 i2000 i1000 i Engine 8.5 N/S N/S N/S N/S N/S N/S 6 Engines 7.5 N/S N/S N/S N/S N/S N/S 12 Engines 6.5 N/S N/S N/S N/S N/S N/S 17

18 Non-Symmetric Full Redistribution for RAID6 Storage Groups The following tables should help you estimate the full redistribution times with non-symmetric configuration changes when using a RAID6 workspace. Avid does not recommend a non-symmetric redistribution when your capacity exceeds 80%. Time to Completion with no Bandwidth (Hours) Capacity Filled 30% Capacity 60% Capacity 80% Capacity Storage Blade i1000 i2000 i1000 i2000 i1000 i2000 i1000 i2000 i1000 i2000 i1000 i Engine N/S N/S N/S N/S N/S N/S Engine N/S N/S 6 12 N/S N/S N/S N/S Engines N/S N/S 8 14 N/S N/S N/S N/S Time to Completion with 100 MB/s of Client Bandwidth per Engine (Hours) Capacity Filled 30% Capacity 60% Capacity 80% Capacity Storage Blade i1000 i2000 i1000 i2000 i1000 i2000 i1000 i2000 i1000 i2000 i1000 i Engine N/S N/S 6 12 N/S N/S N/S N/S Engine N/S N/S N/S N/S N/S N/S N/S Engines N/S N/S N/S N/S N/S N/S N/S 39 Supported Stream Counts with Apple Final Cut Pro Avid has tested Final Cut Pro as a client in the Avid ISIS shared storage environment. Testing was done with Avid ISIS and Final Cut Pro. For supported versions, see the Avid ISIS 7000 ReadMe. There is no Avid restriction on the QuickTime version. Use the QuickTime version recommended in the Final Cut Pro application. The following provides information on how many streams were qualified per client at various resolutions. Avid Interplay Access supports the Mac OSX platform, and through this application Final Cut Pro QuickTime files and projects can be checked into Interplay. Any Interplay workstation can search for these files and edit their Interplay metadata, though there is currently no tightly integrated workflow between Avid editors and Final Cut Pro within Interplay. 18

19 The following list characterizes the setup guidelines for your Final Cut Pro client with Avid ISIS: You need to stay in line with the general client parameters specified for all Avid ISIS Macintosh clients. The following are the specific hardware details used in the Avid testing: Platforms Mac Pro (early 2008) Harpertown Dual Quad-Core 3.0 or 3.2 GHz. Operating system Mac OS and later. Avid ISIS Ethernet connection using the built-in network ports on the Macintosh system. Final Cut Pro editing software was characterized with the AJA KONA 3 hardware. The complete Apple Studio 2 bundle was installed. Verification tests on Apple Color and Sound Track Pro were run to verify Push - Pull capabilities. Final Cut Pro Storage Groups can be configured to either operate using 256 KB or 512 KB chunk sizes. Final Cut Pro clients are supported in ISIS Zones 1 and Zone 2 (not Zone 3). The Avid ISIS Client Manager preference settings follow the same guidelines as for Avid editors. The default setting is set to Medium (limited to resolutions that draw 16 MB/s or less). Use the High setting when working with High Definition media (resolutions that draw higher than 16 MB/s). For data rate specifications, see the data in the following tables. Digidesign Pro Tools software was not tested with Final Cut Pro clients. Scaling the Avid ISIS environment is based on the amount of bandwidth an ISIS engine (or several engines) is able to provide. A single ISIS engine is comprised of 16 storage blades and can produce upwards of 200 MB/s aggregate throughput by serving multiple Final Cut Pro clients simultaneously. Scaling an Avid ISIS beyond a single engine effectively scales in a linear fashion based on a single engines performance. To calculate the rating for your ISIS system, use the following table to define an engine s capabilities based on the chunk size selected when creating a Storage Group and the resolutions in use. Final Cut Pro and Media Composer running on the same Storage Group with Gen 1 switches is not supported, due to performance degradations. Final Cut Pro and Media Composer running on the same RAID 6 Storage Group with Gen 2 switches is not supported, due to performance degradations. Engine Bandwidth Performance (MB/s) with Final Cut Pro Single Engine Engine Switch Generation Chunk Size Storage Group Engine Rating Software Version Final Cut Pro SD ISS KB Mirrored 200 v2.0.1 v Final Cut Pro ProRes SD and HD ISS KB Mirrored 160 v2.0.1 v2.2.2 Final Cut Pro SD ISS KB Mirrored 200 v2.0.1 v2.1.1 Final Cut Pro ProRes SD and HD ISS KB Mirrored 160 v2.0.1 v2.1.1 Final Cut Pro SD ISS KB RAID v2.0.1 v2.2.2 Final Cut Pro ProRes SD and HD ISS KB RAID v2.0.1 v2.2.2 Final Cut Pro and Media Composer SD and HD ISS KB Mirrored 250 v2.2.2 Only Final Cut Pro SD and HD ISS KB Mirrored 300 v2.2.2 Only 19

20 The charts below define the bandwidth used per resolution and the recommended stream count for each. Attempting to increase the number of streams beyond what is shown may result in unexpected results for the Client, but should not impact the ISIS system. Take the following into consideration when reading the following tables. All bandwidth ratings have been adjusted to include up to 8 tracks of 16 bit 48 KHz. Data in this document was obtained using the Final Cut Pro v6.0.5 and v7.0 editing application. The sequence we chose for testing was a two minute sequence with two second audio and video cuts offset by one second. Apple DVCPro s on Mirrored Storage Groups Project Format Number of Streams per client (MB/s) *480 SD DVCPRO25 NTSC *576 SD DVCPRO25 PAL *480 SD DVCPRO50 NTSC N/S 720*576 SD DVCPRO50 PAL N/S Apple ProRes 422 s on Mirrored Storage Groups Project Format Number of Streams per client (MB/s) *720 NQ *576 HQ PAL *720 NQ *486 HQ NTSC *720 HQ N/S 1280*720 HQ *1080 NQ N/S N/S 1920*1080 NQ N/S N/S 1280*720 NQ N/S N/S 1280*720 NQ N/S N/S N/S 1920*1080 NQ N/S N/S N/S 1920*1080 HQ N/S N/S N/S N/S 1280*720 HQ N/S N/S N/S N/S 1920*1080 HQ N/S N/S N/S N/S 1280*720 HQ N/S N/S N/S N/S 1920*1080 HQ N/S N/S N/S N/S 20

21 Apple ProRes 422 s While Playing Out on RAID Storage Groups Project Format Number of Streams on a single per client (MB/s) *486 Proxy 30p *576 Proxy 25p *720 Proxy 25p *576 LT 25p *486 LT 30p *720 Proxy 50p *1080 Proxy 25p *576 NQ *486 NQ *1080 Proxy 30 p o RAID6 Storage Groups only support resolutions of 50 Mb and below. Hardware and Software Used During Testing The following chart describes the hardware and software used during testing this release. Platform OS CPU Memory Editor Version ISIS Client HP z800 Windows 7 64-bit SP1 Dual-Quad 2.93GHz Intel Xeon 6 GB Media Composer v4.0 v2.3 HP z400 Windows Vista 64-bit SP1 Single-Quad 2.93GHz Intel Xeon 6 GB Media Composer v4.0 v2.3 HP z400 Windows 7 64-bit SP1 Single-Quad 2.93GHz Intel Xeon 6 GB Media Composer v5.0 v2.3 HP xw8600 Windows Vista- 64-bit SP1 Dual 3.0GHz Intel Xeon 4 GB Media Composer v4.0 v2.3 HP xw8600 Windows XP 32-bit SP2 Dual 2.66GHz Intel Xeon 4 GB Media Composer v3.5.8 v2.3 Mac Pro x 3GHz Dual-Corel Intel Xeon 4 GB Media Composer v4.0 v2.3 Mac Pro (Nehalem) x 2.66 GHz Dual-Corel Intel Xeon 6 GB Media Composer v5.0 v2.3 21