2730/2730T/5730 Performance Comparison

20 May 2008

Dot Hill Systems Confidential / Covered under NDA

NDA NotificationThis presentation contains information related to projects that are currently in planning and/or development stages. This information represents the current intentions of Dot Hill Systems. However, all aspects of these projects, including, but not limited to funding, availability, shipping dates, configurations, capacities, performance, and all other characteristics are subject to change and/or cancellation without notice.

This material is confidential to Dot Hill Systems and should be disclosed to external entities only under the terms of an executed non-disclosure agreement (NDA).

Distribution of this material to Dot Hill Systems Field Representatives should be done through the Dot Hill Systems NDA process.

The information contained herein is considered privileged, confidential and protected from disclosure. If you are not the intended recipient or their employee/agent responsible for its delivery, you are requested to refrain from any duplication or distribution of this message or its contents, in respect of the rights of the designated recipient and sender, and to delete it from your computer.

2

Dot Hill Systems Confidential / Covered under NDA

About This Presentation• Project Name “Neptune” refers to the 2730/2730T • Project Name “Krypton” refers to the 5730• The performance information contained in this

presentation was obtained within the Engineering Verification Lab using IOMeter

• Actual performance results within specific application use may vary from the contents of this presentation

• This information is provided only as a reference point and no “performance tuning” has been applied

3

Dot Hill Systems Confidential / Covered under NDA

2730 vs. 5730 Quick Reference

4

Sequential Access 2730/2730T 5730 Comments

Read Disk

Bandwidth

(RAID5)

Fail-Over: 550 MB/s

Active/Active: 1100 MB/s

Fail-Over: 790 MB/s

Active/Active: 1580 MB/s

5730 44% faster read throughput

• PCIX/DDR dependent

• CPU independent

Write Disk

Bandwidth

(RAID5)

Fail-Over: 340/380 MB/s

Active/Active: 640/730 MB/s

Fail-Over: 575 MB/s

Active/Active: 980 MB/s

5730 34% faster write throughput

• PCIX/DDR dependent primarily

• CPU dependent on lower end

Read Disk IOps Active/Active: 29K/48K IOPs

Active/Active: 112K/160K IOPs

5730 330% faster read transactions

• PCIX/DDR independent

• CPU dependent

Read Cache Hit

Same Sector

Active/Active: 100K/150K IOPs

Active/Active: 320K/375K IOPs

Same sector transaction rate shows the power of 5730 FC target and CPU low latency performance

Write Disk IOps

(RAID5)

Active/Active: 11K/19K IOPs

Active/Active: 33K/41K IOPs

5730 215% faster write transactions

• PCIX/DDR independent

• CPU dependent

Dot Hill Systems Confidential / Covered under NDA

5730 (5730) Performance Quick Reference

5

Sequential Bandwidth Performance   

Controller Configuration

Host Access

VDisk Type

Measurement Reference / Comments

Dual (Active/Active)

Read All 1580MB/s Four hosts systems connected, each accessing one LUN, two LUNs owned per controller.Note: RAID10 requires additional total drives to meet maximum number.

Dual (Active/Active)

Write RAID0RAID5RAID6RAID10RAID50

1271 MB/s987 MB/s914 MB/s882 MB/s1003 MB/s

Sequential Transaction Performance   

Controller Configuration

Host Access

VDisk Type Measurement Comments / Reference

Dual (Active/Active) Read RAID5 143.1K IO/s160K IO/s

Four hosts systems connected, each accessing one LUN, two LUNs owned per controller.

Single (Fail-Over)Dual (Active/Active)

Write RAID5 39.4K IO/s25.5K IO/s

Dual (Active/Active) Same Sector

N/A 375K IO/s 512B read same sector (cache hit) access using four hosts systems connected, each accessing one LUN, two LUNs owned per controller.

Random Transaction Performance

Controller Configuration

Host Access

VDisk Type

Measurement

Dual (Active/Active) Read All 24.9K IO/sSingle (Fail-Over)Dual (Active/Active)

Write RAID5RAID6RAID0RAID10

5.4K IO/s4.1K IO/s3.1K IO/s13.0K IO/s8.3K IO/s

Dot Hill Systems Confidential / Covered under NDA

Krypton AA SAS 48 DrivesSequential Performance (Base-2)

1696

5

2548

1

0.0

5000.0

10000.0

15000.0

20000.0

25000.0

30000.0

0.5K 1K 2K 4K 8K 16K 32K 64K 128K 256K 512K 1M

Neptune-T Write

Krypton Write(IOPs)

(block size)

K100B24p vs J200B26pVdisk = 12-Drive RAID54 Vdisk, 2/Cntl, 1 LUN/VdiskWin2003 Server MPIO4 Port x 4Gb FC switchedSingle Client access/LUNQd = 16/LUN

Krypton Single Controller SAS 48 DrivesSequential Performance (Base-2)

1785

3

3940

9

0.0

5000.0

10000.0

15000.0

20000.0

25000.0

30000.0

35000.0

40000.0

45000.0

0.5K 1K 2K 4K 8K 16K 32K 64K 128K 256K 512K 1M

Neptune-T Write

Krypton Write(IOPs)

(block size)

K100B24p vs J200B26pVdisk = 12-Drive RAID64 Vdisk, 1 LUN/VdiskWin2003 Server MPIO4 Port x 4Gb FC switchedSingle Client access/LUNQd = 16/LUN

5730’s storage controller processor accounts for the higher sequential write transaction performance both Active/Active and failed over. 5730 sustains between 150% and 220% higher write transaction performance than 2730T at deeper queued small block host request sizes.

2730T vs. 5730 in RAID 5 & 6RAID 5 & 6 Sequential Write with 48 drives

Dot Hill Systems Confidential / Covered under NDA

2730T vs. 5730 in RAID 5 & 6RAID 5 & 6 Sequential READ with 48 drives

Krypton AA SAS 48 DrivesSequential Performance (Base-2)

0.0

200.0

400.0

600.0

800.0

1000.0

1200.0

1400.0

1600.0

0.5K 1K 2K 4K 8K 16K 32K 64K 128K 256K 512K

Neptune-T Read

Krypton Read(MB/s)

(block size)

K100B24p vs J200B26pVdisk = 12-Drive RAID54 Vdisk, 2/Cntl, 1 LUN/VdiskWin2003 Server MPIO4 Port x 4Gb FC switchedSingle Client access/LUNQd = 16/LUN

5730 controller read bandwidth is 800MB/s per controller versus 2730T peaking at 570MB/s. 5730 sustains 40% higher read throughput then 2730T at large block sizes.

The Active/Active 5730 read performance in the curve is limited by the four port FC host. 5730 Active/Active read performance can sustain 1600MB/s with multiple host systems accessing.

Krypton Single Controller SAS 48 DrivesSequential Performance (Base-2)

0.0

100.0

200.0

300.0

400.0

500.0

600.0

700.0

800.0

900.0

0.5K 1K 2K 4K 8K 16K 32K 64K 128K 256K 512K

Neptune-T Read

KryptonRead(MB/s)

(block size)

K100B24p vs J200B26pVdisk = 12-Drive RAID64 Vdisk, 1 LUN/VdiskWin2003 Server MPIO4 Port x 4Gb FC switchedSingle Client access/LUNQd = 16/LUN

Dot Hill Systems Confidential / Covered under NDA

5730 Scalability Testing (24 – 60 Drives)

Active/Active Controller Random Read/Write

Krypton AA SAS DrivesRandom Performance (Base-2)

13163

0.0

1000.0

2000.0

3000.0

4000.0

5000.0

6000.0

7000.0

8000.0

9000.0

10000.0

11000.0

12000.0

13000.0

14000.0

0.5K 1K 2K 4K 8K 16K 32K 64K 128K 256K 512K 1M

60 Drives Read 48 Drives Read

36 Drives Read 24 Drives Read(IOPs)

(block size)

K100B32pRAID5 Vdisk 4 Vdisk, 2/Cntl, 1 LUN/VdiskWin2003 Server MPIO 4 Port x 4Gb FC switchedSingle Client access/LUNQd = 64/LUN

Krypton AA SAS DrivesRandom Performance (Base-2)

0.0

500.0

1000.0

1500.0

2000.0

2500.0

3000.0

3500.0

4000.0

4500.0

5000.0

0.5K 1K 2K 4K 8K 16K 32K 64K 128K 256K 512K 1M

60 Drives Write 48 Drives Write

36 Drives Write 24 Drives Write (IOPs)

(block size)

K100B32pRAID5 Vdisk 4 Vdisk, 2/Cntl, 1 LUN/VdiskWin2003 Server MPIO 4 Port x 4Gb FC switchedSingle Client access/LUNQd = 64/LUN

Drive numbers have a much larger affect on random performance. For reads there is almost a direct correlation between the total number of drives accessed and the total random transaction IOPS. The drive random access performance is the limiting factor for reads in general.

Writes top out at 48 drives. Additional drives won’t improve random write numbers. The limit becomes the controller processing and cache algorithm.

Dot Hill Systems Confidential / Covered under NDA

5730 Max Configuration (108 Drive)Sequential Reads/Writes for Active/Active (Throughput & IOPS)

Krypton AA SAS 108 DrivesSequential Performance (Base-2)

1436

980

0.0

100.0

200.0

300.0

400.0

500.0

600.0

700.0

800.0

900.0

1000.0

1100.0

1200.0

1300.0

1400.0

1500.0

0.5K 1K 2K 4K 8K 16K 32K 64K 128K 256K 512K 1M

Sum 2x Host Reads

Sum 2x Host Writes(MB/s)

(block size)

K100A17pVdisk = 4xRAID50x27Drives(3x9)1 LUN / Vdisk, Qd = 8 / LUNTwo Win2003 Hosts MPIO2 port x 4Gb FC / HostEach host accesses all 8 LUNs

Krypton AA SAS 108 DrivesSequential Performance (Base-2)

1431

3625

158

0.0

10000.0

20000.0

30000.0

40000.0

50000.0

60000.0

70000.0

80000.0

90000.0

100000.0

110000.0

120000.0

130000.0

140000.0

150000.0

0.5K 1K 2K 4K 8K 16K 32K 64K 128K 256K 512K 1M

Sum 2x Host Reads

Sum 2x Host Writes(IOPs)

(block size)

K100A17pVdisk = 4xRAID50x27Drives(3x9)1 LUN / Vdisk, Qd = 32 / LUNTwo Win2003 Hosts MPIO2 port x 4Gb FC / HostEach host accesses all 8 LUNs

The RAID50 VDisk in this configuration is 27-drives, with 3 sub-arrays of 9-drive RAID5. In this test configuration two dual port host systems are connected through the switch to 5730. Each host accesses the 4 LUNs presented by the 5730 Active/Active RAID system. Each host issues a queue depth / LUN, therefore each LUN sees 2x the total queue depth of each host.