The media applications workload covers a broad swath of applications that spans video rendering, broadcasting, streaming and editing. In the case of the first three applications typically you have hundreds or thousands of hosts sharing access to a huge volume of video content. For this reason high bandwidth (GB/s) in combination with low cost of $/GB as well as ease of management and large scale-out capability are mandatory. In addition, in the streaming use case, we are starting to see some object use cases pop up. For these reasons, the loosely coupled scale-out architecture is the correct architecture choice for this workload.
Video editing has a different workload profile all together. In this case, there are a relatively small number of hosts that need small block, low latency access to a smaller set of media files. This use drives very low latency and $/IOPS requirements. For these reasons, the scale-up/down architecture is the correct architecture choice for this workload.
The Spiderchart below shows the distribution and weighting of the primary workload requirements for this use case.