1. Scope
2. Executive SummaryThis document summarizes current performance test data of Promise Vess R2600, as references for Product Marketing. This document will highlight real world video performance, Configurations, Topologies and also real world applications.
Vess R2600performance data is summarized in the following tables:
Table 1 – Single Controllervs. Dual Controller Playback Test Results (OSX 10.10.2)
Notes:
Data Rate
MBs
Single Controller
Dual Controller
App
Load
FCPX 10.1.3
PreRes4444 10bit QuadHD 3840x2160 @59.94fps.mov
304.9
1
1
PreRes4444 10bit QuadHD 3840x2160 @50fps.mov
254.4
1
2
PreRes4444 10bit QuadHD 3840x2160 @29.97fps.mov
152.5
2
3
PreRes4444 10bit QuadHD 3840x2160 @23.98fps.mov
122.1
3
6
Uncompressed 10bit 1920x1080@29.97fps.mov
165.9
2
3
Uncompressed 10bit 1920x1080@23.97fps.mov
132.6
3
6
ProRes 422 HQ (1080 @29.97fps).mov
27.8
11
22
DVCPro HD 1280x1080 @29.97fps.mov
14.6
21
42
The purpose is to test the performance of Promise Vess R2600 single controller vs dual controller using A/V streaming loads.
Platform
Mac OSX 10.10.2
File System
XFS
Topology
Four 10Gbit NAS clients
Storage
Vess R2600tiD Version: 1.04.0000.01 Build Date: Mar 5, 2015
Software
Apple Final Cut Pro X –10.1.3
Video Formats
PreRes4444 10bit QuadHD 3840x2160 @59.94fps QuickTime media
PreRes4444 10bit QuadHD 3840x2160 @50fps QuickTime media
PreRes4444 10bit QuadHD 3840x2160 @29.97fps QuickTime media
PreRes4444 10bit QuadHD 3840x2160 @23.98fps QuickTime media
Uncompressed 10bit 1920x1080@29.97fpsQuickTime media
Uncompressed 10bit 1920x1080@23.97fpsQuickTime media
ProRes422 HQ (1080 @29.97fps)QuickTime media
DVCPro HD 1280x1080 @29.97fpsMedia Workload
Playback
Ingest
Ingest& playback mixed
4. Test Environment & Topology* : Use Terminal “dd” command to simulate ingesting.
There are two 10Gbit Ethernet interfaces on each controller of Vess R2600tiD. We need to setup all the Mac clients and Vess R2600tiD in the same switch and give them some IP addresses. For example: give Vess R2600tiD IP address of 10.0.10.1 and 10.0.10.2. And set the IP address of Mac clients be 10.0.10.5, 10.0.10.6… and so on. After that, the Mac clients can access the storage of Vess R2600tiD via Samba by “Connect to Server” with smb://10.0.10.1 or smb://10.0.10.2.
Figure1 – 10Gbit NAS Test Topology – Single Controller
In dual controller case, we also could put them all in the same sub-net. For example: give Vess R2600tiD controller1 IP address of 10.0.10.1 and 10.0.10.2 and controller2 IP address of 10.0.10.3 and 10.0.10.4. And set the IP address of Mac clients be 10.0.10.5, 10.0.10.6… and so on. After that, the Mac clients can access the storage of Vess R2600tiD controller1 via Samba by “Connect to Server” with smb://10.0.10.1 or smb://10.0.10.2 and controller2 with smb://10.0.10.3 or smb://10.0.10.4.
Figure
2 – 10Gbit NAS Test Topology – Dual Controller
Vess R2600tiD: Dual controller, 16GB memory per controller, Redundancy Type:Active-Active.
Controller: Adaptive Writeback Cache enabled, LUNAffinity disabled,
ALUA disabled and ForcedReadAhead disabled.
Disk Pool: RAID Level: RAID5 and Stripe Size: 1MB.
Drives: Controller1: 16 HGSTHUS724030ALS640 3TB drives for
Disk Pool (DP1) with RAID5 and Share Disk (SD1)
Controller2: 16 HGST HUS724020ALS640 2TB drives for
Disk Pool (DP2) with RAID5 and Share Disk (SD2)
Storage subsystem configuration
DP1(R5)-SD1
DP1(R5)-SD1
DP1(R5)-SD1
DP1(R5)-SD1
DP1(R5)-SD1
DP1(R5)-SD1
DP1(R5)-SD1
DP1(R5)-SD1
DP1(R5)-SD1
DP1(R5)-SD1
DP1(R5)-SD1
DP1(R5)-SD1
DP1(R5)-SD1
DP1(R5)-SD1
DP1(R5)-SD1
DP1(R5)-SD1
DP2(R5)-SD2
DP2(R5)-SD2
DP2(R5)-SD2
DP2(R5)-SD2
DP2(R5)-SD2
DP2(R5)-SD2
DP2(R5)-SD2
DP2(R5)-SD2
DP2(R5)-SD2
DP2(R5)-SD2
DP2(R5)-SD2
DP2(R5)-SD2
DP2(R5)-SD2
DP2(R5)-SD2
No frame drop for ~1 hour streaming.
OS-X version 10.9.X will not support as many video streams as OS-X 10.10.X as it does not support SMB v3.0. Also for best performance a change is required to the TCP/IP stack.
For runtime, enter the following command.
sudo sysctl -w net.inet.tcp.delayedack=0
This change will not survive a reboot. To make the change persistent, create a file named/etc/sysctl.conf, in the file place the command
net.inet.tcp.delayedack=0
This change is not necessary in OS-X 10.10.X.
