- Community Home
- >
- Storage
- >
- Entry Storage Systems
- >
- Disk Enclosures
- >
- FC10 Operation
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
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
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-21-2001 01:09 AM
тАО11-21-2001 01:09 AM
I would like to ask about the FC10 operation.
Since the link is Fibre channel and the disks are SCSI daisy chained then there is no way where I can read in parallel from each disk.Is this true?
I believe that such thing can perfromed only when using LUNs where you can have up two disks work as one through different controller. Such system could be FC60 or XP series.
How the kernel parameters affect the Fibre Channel operation?
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-21-2001 01:50 AM
тАО11-21-2001 01:50 AM
Re: FC10 Operation
As for kernel parms... I can't think of any I'd use specifically for fibre channel - but I'm happy to be proved wrong.
HTH
Duncan
I am an HPE Employee
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-21-2001 01:58 AM
тАО11-21-2001 01:58 AM
Re: FC10 Operation
Can I stripe along 10 disks?
How can I define the striping size for ORACLE?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-21-2001 02:42 AM
тАО11-21-2001 02:42 AM
Re: FC10 Operation
Your config - how many FC HBAs you have, how many FC10s you have and whether your FC10s have 2 LCCs
Your availability requirement... (Do you need to mirror your data?)
Your Database - what the expected profile of your database is (OLTP or DSS? many small random writes/large sequential writes etc.)- the attached info is from Oracle's 'Designing & Tuning for Performance' Manual.
______________________________________________
Striping Disks with Operating System Software
As an alternative to striping disks manually, use operating system utilities or third-party tools, such as logical volume managers, or use hardware-based striping.
With utilities or hardware-based striping mechanisms, the main factors to consider are stripe size, number of disks to stripe across (which defines the stripe width), and the level of concurrency (or level of I/O activity). These factors are affected by the Oracle block size and the database access methods.
Table 20-14 Minimum Stripe Size
Disk Access Minimum Stripe Size
Random reads and writes
The minimum stripe size is twice the Oracle block size.
Sequential reads
The minimum stripe size is twice the value of DB_FILE_MULTIBLOCK_READ_COUNT.
Table 20-15 Typical Stripe Size
Concurrency I/O Size Typical Stripe Size
Low
Small
k * DB_BLOCK_SIZE
Low
Large
k * DB_BLOCK_SIZE
High
Small
k * DB_BLOCK_SIZE
High
Large
k * DB_BLOCK_SIZE * DB_FILE_MULTI_BLOCK_READ_COUNT
Where k = 2,3,4...
In striping, uniform access to the data is assumed. If the stripe size is too large, then a hot spot may appear on one disk or on a small number of disks. Avoid this by reducing the stripe size, thus spreading the data over more disks.
Consider an example in which 100 rows of fixed size are evenly distributed over 5 disks, with each disk containing 20 sequential rows. If your application only requires access to rows 35 through 55, then only 2 disks must perform the I/O. At a high rate of concurrency, the system may not be able to achieve the desired level of performance.
Correct this problem by spreading rows 35 through 55 across more disks. In the current example, if there were two rows per block, then we could place rows 35 and 36 on the same disk, and rows 37 and 38 on a different disk. Taking this approach, we could spread the data over all the disks and I/O throughput would improve.
HTH
Duncan
I am an HPE Employee
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-21-2001 02:46 AM
тАО11-21-2001 02:46 AM
Re: FC10 Operation
Concurrency I/O Size Typical Stripe Size
------------------------------------------
Low Small k * DB_BLOCK_SIZE
Low Large k * DB_BLOCK_SIZE
High Small k * DB_BLOCK_SIZE
High Large k * DB_BLOCK_SIZE * DB_FILE_MULTI_BLOCK_READ_COUNT
I am an HPE Employee
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-21-2001 02:49 AM
тАО11-21-2001 02:49 AM
SolutionConcurrency | I/O Size | Typical Stripe Size
------------------------------------------
Low | Small | k * DB_BLOCK_SIZE
Low | Large | k * DB_BLOCK_SIZE
High | Small | k * DB_BLOCK_SIZE
High | Large | k * DB_BLOCK_SIZE * DB_FILE_MULTI_BLOCK_READ_COUNT
I am an HPE Employee