- Community Home
- >
- Servers and Operating Systems
- >
- HPE ProLiant
- >
- ProLiant Servers (ML,DL,SL)
- >
- Migrate band size RAID 5
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Discussions
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
Community
Resources
Forums
Blogs
- 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
01-14-2019 10:35 AM
01-14-2019 10:35 AM
Migrate band size RAID 5
Hello, good afternoon.
I wanted to ask you what could be the best optimization and efficiency for an 8×6 TB RAID5 array.
Currently I have this band size, and now I'm going to dedicate this RAID to download through P2P, so it will have an intense work of reading, but less than 80/20 writing.
I've been looking, and there are people who say to lower the band size to KiB, but I would like to know your opinion in order to optimize the RAID as much as possible.
Thank you!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-15-2019 08:56 PM
01-15-2019 08:56 PM
Re: Migrate band size RAID 5
When distributing data across multiple physical drives (striping), the strip size is the amount of data that is written to each physical drive. The full stripe size refers to the combined size of all the strips across all physical drives, excluding parity-only drives.
The maximum strip size changes dynamically and is reduced for arrays with a large number of data drives or with smaller controller cache sizes. The controller must be able to read an entire strip of data at a time into cache memory during transformation. Available memory is the limiting factor and also check on the read/write settings on the cache module.
Another thing that we should keep in mind is the about the job types (sequential or random). For random jobs then it is advisable to keep the stripe size large but keep it small for sequential jobs.
I am an HPE employee.
[Any personal opinions expressed are mine, and not official statements on behalf of Hewlett Packard Enterprise]
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-16-2019 03:04 AM
01-16-2019 03:04 AM
Re: Migrate band size RAID 5
@BPSingh wrote:When distributing data across multiple physical drives (striping), the strip size is the amount of data that is written to each physical drive. The full stripe size refers to the combined size of all the strips across all physical drives, excluding parity-only drives.
The maximum strip size changes dynamically and is reduced for arrays with a large number of data drives or with smaller controller cache sizes. The controller must be able to read an entire strip of data at a time into cache memory during transformation. Available memory is the limiting factor and also check on the read/write settings on the cache module.
Another thing that we should keep in mind is the about the job types (sequential or random). For random jobs then it is advisable to keep the stripe size large but keep it small for sequential jobs.
Hello, thank you for your reply!
As for the configuration of the hardware controller (P440/4GB), currently all the cache is assigned to write, nothing to read. The server has a RAM of 32GB.
On sequential or random readings, most readings will be random, so as you say, I think the band size is correct.
If you have any more ideas on how many configurations, please let me know. Thank you!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-16-2019 03:10 AM
01-16-2019 03:10 AM
Re: Migrate band size RAID 5
@BPSinghAnother question that comes to mind. Do you know if the Windows native defragmenter would do a good job defragmenting RAID5 8×6TB hardware?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-16-2019 05:31 PM
01-16-2019 05:31 PM
Re: Migrate band size RAID 5
The controller cache size is 4 GB. The read/write settings on the cache can be adjusted from Smart Storage administrator, you may set it to 25% read and 75% write or 50/50 depending on your requirement. Please be informed that the system memory (32GB) won't be used for this.
Disk Defragmenter is known to increase data access speeds but however not sure about its affect on RAID performance. You may have to check with the OS vendor for this.
I am an HPE employee.
[Any personal opinions expressed are mine, and not official statements on behalf of Hewlett Packard Enterprise]
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-17-2019 04:25 AM
01-17-2019 04:25 AM
Re: Migrate band size RAID 5
Ok, thanks!!!!!!