https://community.hpe.com/t5/operating-system-hp-ux/how-wide-can-oracle-asm-stripes-be-and-other-cache-centric/m-p/4563175#M650063 Cache-Centric Arrays like Hitachi Tier-1 arrays and derivatives (aka XP12000, XP24000) always have that golden rule to stripe wide and "thin".<BR /><BR />Since the switch to ASM storage - we've seen quite a substantial toll from our Database Servers to our aptly provisioned XP array but at the same time saw generally a substantial increase in performance and scalability.<BR /><BR />There are however environments that have grown substantially and since our LDEVs (or LUN sizes) are ~50 Gigs each - we now have ASM Disksets (under VxVM as raw unitary volumes of course per Symantec/Oracle Best Practice) that could exceed 1024 disks.<BR /><BR />My question -- how far wide can ASM striped I/O continue to scale? Will there be penalties growing even wider with such smaller disks? Will it intoruduce cache incoherency at some point that we'll have to do "cache partitioning" for each large DB Server?<BR /><BR />I've heard rumours of overly striping accross many front-ends and accross many LUNS can sometimes result in flooding the cache on certain cache-centric arrays -- True or Myth?<BR /><BR />TIA for your views... perceieved or proven.<BR /><BR /> Tue, 12 Jan 2010 21:29:33 GMT Alzhy 2010-01-12T21:29:33Z https://community.hpe.com/t5/operating-system-hp-ux/how-wide-can-oracle-asm-stripes-be-and-other-cache-centric/m-p/4563175#M650063 Cache-Centric Arrays like Hitachi Tier-1 arrays and derivatives (aka XP12000, XP24000) always have that golden rule to stripe wide and "thin".<BR /><BR />Since the switch to ASM storage - we've seen quite a substantial toll from our Database Servers to our aptly provisioned XP array but at the same time saw generally a substantial increase in performance and scalability.<BR /><BR />There are however environments that have grown substantially and since our LDEVs (or LUN sizes) are ~50 Gigs each - we now have ASM Disksets (under VxVM as raw unitary volumes of course per Symantec/Oracle Best Practice) that could exceed 1024 disks.<BR /><BR />My question -- how far wide can ASM striped I/O continue to scale? Will there be penalties growing even wider with such smaller disks? Will it intoruduce cache incoherency at some point that we'll have to do "cache partitioning" for each large DB Server?<BR /><BR />I've heard rumours of overly striping accross many front-ends and accross many LUNS can sometimes result in flooding the cache on certain cache-centric arrays -- True or Myth?<BR /><BR />TIA for your views... perceieved or proven.<BR /><BR /> Tue, 12 Jan 2010 21:29:33 GMT https://community.hpe.com/t5/operating-system-hp-ux/how-wide-can-oracle-asm-stripes-be-and-other-cache-centric/m-p/4563175#M650063 Alzhy 2010-01-12T21:29:33Z https://community.hpe.com/t5/operating-system-hp-ux/how-wide-can-oracle-asm-stripes-be-and-other-cache-centric/m-p/4563176#M650064 Oracle 11g ASM Scalability <BR /><BR />63 disk groups<BR />10,000 disks<BR />1 million files per disk group<BR />4PB per disk<BR />Max DB size:<BR />with external redundancy 140PB<BR />with normal redundancy 42PB<BR />With high redundancy 15PB<BR /><BR />For XP12000 with ASM, you may want to review the white paper and webinar available at <BR /><A href="http://h71028.www7.hp.com/enterprise/us/en/solutions/storage-customer-focused-testing-oracle.html" target="_blank">http://h71028.www7.hp.com/enterprise/us/en/solutions/storage-customer-focused-testing-oracle.html</A><BR /><BR /><A href="http://www.oracle.com/technology/products/database/asm/pdf/HP-UX%20-ASM-StgWorks-MP%2002-06.pdf" target="_blank">http://www.oracle.com/technology/products/database/asm/pdf/HP-UX%20-ASM-StgWorks-MP%2002-06.pdf</A><BR /><BR /><BR /> Thu, 14 Jan 2010 07:41:21 GMT https://community.hpe.com/t5/operating-system-hp-ux/how-wide-can-oracle-asm-stripes-be-and-other-cache-centric/m-p/4563176#M650064 Sameer_Nirmal 2010-01-14T07:41:21Z