Re: AU size for multi-TB DB

From: Stefan Koehler <contact_at_soocs.de>
Date: Thu, 28 Mar 2024 15:04:00 +0100 (CET)
Message-ID: <1899415010.438670.1711634640625_at_ox.hosteurope.de>


Hello Laurentiu,
are you still using Oracle 10g? If not, Oracle ASM uses variable size extents, e.g. check here: https://docs.oracle.com/en/database/oracle/oracle-database/19/ostmg/asm-intro.html#GUID-1E5C4FAD-087F-4598-B959-E66670804C4F

"Each extent resides on an individual disk. Extents consist of one or more allocation units (AU). To accommodate increasingly larger files, Oracle ASM uses variable size extents. Variable size extents enable support for larger Oracle ASM data files, reduce SGA memory requirements for very large databases, and improve performance for file create and open operations. The initial extent size equals the disk group allocation unit size and it increases by a factor of 4 or 16 at predefined thresholds. The various extent sizes are described in this topic. ...
..."

Best Regards
Stefan Koehler

Independent Oracle performance consultant and researcher Website: www.soocs.de
Twitter: _at_OracleSK

> Laurentiu Oprea <laurentiu.oprea06_at_gmail.com> hat am 28.03.2024 14:08 CET geschrieben:
>
>
> Dear oracle community,
>
>
> Did anyone followed and tested recommendations from oracle note: Deployment of very large databases (10TB to PB range) with Automatic Storage Management (ASM) (Doc ID 368055.1)
> when deployed a multi-TB database (in my scenario 100+TB and 700+TB) ?
>
> If yes and run some tests I appreciate if you can share some results / conclusions
>
> Thank you

--
http://www.freelists.org/webpage/oracle-l
Received on Thu Mar 28 2024 - 15:04:00 CET

Original text of this message