HPE GreenLake Administration
- Community Home
- >
- Storage
- >
- Legacy
- >
- Disk
- >
- SAS 6G vs. 3G for controllers/disks
Disk
1833019
Members
2249
Online
110049
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-11-2010 10:47 AM
02-11-2010 10:47 AM
SAS 6G vs. 3G for controllers/disks
Hello Disk Experts!
A few questions for you regarding SAS 6G vs. 3G. I'm using a RAID 5 configuration, so please keep this in mind for the below.
From what I understand, a spinning hard drive (vs. SSD) will never hit anywhere near the limit for 3G speed for sustained read/writes.
1) Is there any reason to get SAS 6G spinning hard drives, and if so, in what situations and why?
From what I can gather, and these are rough numbers from Seagate's Cheetah drives, a SAS 10K drive can push out a sustained 88MB/sec/drive, and a SAS 15K drive can do about 120MB/sec/drive.
If a 3G controller can maintain it's theoretical 3G throughput (doubtful), then I would need at least four SAS 10K drives or three 15K SAS drives before I could possibly see any real benefit to 6G.
2) Is this logic flawed, and if so, how?
3) What is the maximum sustained throughput on a 6G controller, e.g., the HP P410 (462862-B21)?
4) In what situations does it make sense to use a 6G controller with 3G drives?
Many thanks!
A few questions for you regarding SAS 6G vs. 3G. I'm using a RAID 5 configuration, so please keep this in mind for the below.
From what I understand, a spinning hard drive (vs. SSD) will never hit anywhere near the limit for 3G speed for sustained read/writes.
1) Is there any reason to get SAS 6G spinning hard drives, and if so, in what situations and why?
From what I can gather, and these are rough numbers from Seagate's Cheetah drives, a SAS 10K drive can push out a sustained 88MB/sec/drive, and a SAS 15K drive can do about 120MB/sec/drive.
If a 3G controller can maintain it's theoretical 3G throughput (doubtful), then I would need at least four SAS 10K drives or three 15K SAS drives before I could possibly see any real benefit to 6G.
2) Is this logic flawed, and if so, how?
3) What is the maximum sustained throughput on a 6G controller, e.g., the HP P410 (462862-B21)?
4) In what situations does it make sense to use a 6G controller with 3G drives?
Many thanks!
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-18-2010 11:11 PM
02-18-2010 11:11 PM
Re: SAS 6G vs. 3G for controllers/disks
When looking at how long a disk I/O takes you have the time to seek but also the time to transfer the data from the disk to the controller. 3 Gb/s gives you a maximum theoretical transfer rate of ~300 MB/s. a 6Gb/s link should double that to ~600 MB/s
If you are doing I/Os with large transfer size say 1 MB (MegaByte) then the time it takes for one transfer is 3.3 ms at 3 Gb/s and 1.7 ms at 6 Gb/s. Assuming an average seek time of 3.5 ms then an I/O would take about 6.8 for 3 Gb and 5.2 ms for 6 Gb drives and controllers. This timing is greatly simplified. This give you a I/O rate of 147 I/Os per second for the 3 Gb and 192 I/Os per second for the 6 Gb drive and controller.
Of course if your data size is much smaller then the difference would be smaller. Looking at an 8K transfer size we get an I/O rate of 283 and 284 I/O per second for 3 Gb and 6 Gb respectively.
With RAID5 you also need to look at time to rebuild the raid set after a failure. While the raid set is rebuilding you can experience significant performance reductions. Again a faster transfer time will reduce this time.
Hope this helps
If you are doing I/Os with large transfer size say 1 MB (MegaByte) then the time it takes for one transfer is 3.3 ms at 3 Gb/s and 1.7 ms at 6 Gb/s. Assuming an average seek time of 3.5 ms then an I/O would take about 6.8 for 3 Gb and 5.2 ms for 6 Gb drives and controllers. This timing is greatly simplified. This give you a I/O rate of 147 I/Os per second for the 3 Gb and 192 I/Os per second for the 6 Gb drive and controller.
Of course if your data size is much smaller then the difference would be smaller. Looking at an 8K transfer size we get an I/O rate of 283 and 284 I/O per second for 3 Gb and 6 Gb respectively.
With RAID5 you also need to look at time to rebuild the raid set after a failure. While the raid set is rebuilding you can experience significant performance reductions. Again a faster transfer time will reduce this time.
Hope this helps
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP