Professional Documents
Culture Documents
The interleaving Grid disks concepts is based on dividing the grid disks in multiple parts,
thus protecting the perfomance across them..
In other words; by using the interleaving option in Exadata the cell disks are intelligently
divided in to grid disks which are equal in performance.
In this interleaving disk concept, Exadata actually takes benefit of Zone Bit Recording
(ZBR) to have higher transfer IO bandwith on outer part of the hard disks.. In addittion to
that , Exadata manages the allocation of disk parts using its interleaving option in order
to have equal disk portion in terms of performance..
Following shape, on the other hand; describes the structure of a disk, that uses
ZBR(Zone Bit Recording).
Red: The closest to the center
Green : In the middle, have more sectors than Red.
Grey: Farthest to the center, have more sectors than Red.
As you above, as the distance from the center increases, the number of sectors in a
given angle also increases. As standard hard disks have a constant angular velocity,
which means regardless of where the heads are, the same speed is used to turn the
media.. So by knowing this, we can say that; the path that a disk would travers in a 360
degree turn will be more in outer part of the disk, so more data will be read.. This
will increase linear velocity.
Exadata brings a solution for that.. Actually it s an option, optional thing called
Interleaving.
Interleaving is defined in Cell disk layer.
Note that: Whether you choose to use no interleaving or interleavig, Oracle will allocate
the first set of extents on the outer part of the physical disk..
Oracle has two options for Interleaving . Normal redundancy and High redundancy..
These redundancies are not like ASM redundancy.. They have different meaning..
In Normal Redundancy, Oracle divides your grid disk into two ranges of disk tracks. In
High Redundancy: Oracle divides your grid disk into three ranges of disk tracks..
After creating the cell disk , we can place the grid disks on this Cell disk with the
following commands..
As represented above, the cell disk named interleaving_erman is divided into 2 equal
portion. Grid disk DATA1 is placed on the ranges of disk track, painted red.. Grid Disk
RECO is placed on the ranges of disk tracks, painted green. In this scenario; DATA1
and RECO are considered almost equal in overall performance. Note that, the ranges in
above shape can be changed accoring to the Grid Disk size specified.
What happens here is, the disk is divided in two parts..(%50 - %50 ).. And in each part,
the disk is divided again..
So if we have 600G cell disk with interleaving normal redundancy and if we create two
Grid Disks in sequence.. (Grid Disk A with 250G, Grid Disk B with 350G) it happens as
follows;
Oracle will divide the disk in to 300 gb pieces.
In the first part : Oracle will place 125 G of Grid Disk A(most outer) -> RED , and 175 G
of Grid Disk B -> GREEN
In the second part: Oracle will place 125 GB of Grid Disk A -> RED , and 175 G of Grid
Disk B -> GREEN.
So the size of the rings will differ.. I didnt do the math, but this should be a good
approach to catch the same IO rates for the interleaving disks..
In brief,
Oracle emphasize that, different ASM disk groups can share the Cell Disks without a
performance bias, if you prefer to use Interleaving .. In other words, by using
interleaving, Oracle can divide the Cell Disk in to the parts which are equal in
performance(really equal?, it seems not exactly but almost equal to me :))
The idea behind that is ZBR. In ZBR, the tracks in the same zone are recorded with the
same read/write rate.. So, Oracle's disk dividing operation provides using this zones
intelligently..