- Community Home
- >
- Storage
- >
- HPE Nimble Storage
- >
- Array Performance and Data Protection
- >
- Re: Deploying SAS 9.3 Data Analytics - Performance...
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
11-12-2015 05:35 PM
11-12-2015 05:35 PM
The volume in question will be a stand-alone volume within Nimble. Within Windows, we'll format it with an allocation unit size of 64K since it will primarily be doing large sequential reads. However, not sure what performance policy to apply to this volume within Nimble. Anyone with experience with this who can lend a hand?
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-16-2016 12:49 PM
02-16-2016 12:49 PM
SolutionBased on this SAS KB 51659, (from a past life), your key line in "SAS World" is pagesize: (Much like MS SQL)
- -pagesize
Specifies the size of the page for I/O operation (for example, 8k, 64k, 128k). See the note on -pagesize below. If –pagesize is not specified the default is 8k.
So basically it's 8K, unless someone is changing it. (I wouldn't.) Which equates to SQL 2012 Data. (8K, Compression On, Cache On)
Remember, if you're doing an RDM or VMDK, don't bother with block sizes outside of 4K.
If you present a volume via Windows iSCSI Initiator, then you can leverage the 8K block size.
I'm pretty sure that's what you need. If anyone else has learned different, please let me know.