Академический Документы
Профессиональный Документы
Культура Документы
John Clarke
Oracle Architect
Centroid
Now What?
One Size
Fits all
Tuning EBS
On Exadata
Why Not?
Best
Practices
Todays Goal
Exadata fundamentals
What makes Exadata Different
Exadata Software Features
How the Features work with EBS
Exadata Hardware
Compute Grid
Dual-core x64 servers running
Oracle 11gR2
InfiniBand Network
Redundant 40 Gb/s switches
Unified fabric for storage and
servers
Storage Grid
12 HP or HC SAS drives
384Gb PCIe Flash/cell
Data mirrored across cells with
ASM
Exadata Software
Exadata Software Goals
Fully and evenly utilize all
Computing resources in
Exadata Database Machine
to eliminate bottlenecks and
deliver consistent high
performance
Smart Scan
Probably the most important software feature with Exadata
One of several cell offload features in Exadata
cell offload is defined as Exadatas shifting of database work
from the database servers to Exadata storage servers
Goal of Smart Scan is to perform the majority of IO processing on
storage servers and return smaller amounts of data from the
storage infrastructure to the database servers
IO no longer a bottleneck
Provides dramatic performance improvements for eligible SQL
operations (full table scans, fast full index scans, joins, etc.)
Smart Scan is implemented automatically on Exadata
Smart Scan only works on Exadata
An iDB command is
constructed and sent to
Exadata cells
IO: Non-Exadata
IO: Exadata
Smart Scan
Filtering operations are offloaded to the Exadata storage cell
Column Filtering
Predicate Filtering (i.e., row filtering)
Join Filtering
Only requested rows and columns are returned to the database
server
Significantly less IO transfer over storage network
Less memory and CPU required on database tier nodes
Rows/columns retrieved to users PGA via direct path read
mechanism, not through buffer cache.
Large IO requests dont saturate buffer cache
Performance is
largely IO waits
Customers around
the world have
performance issues
Oracle over-indexes
and over-hints to
force index scans
No Smart Scan
SBR/MBR
SBR/MBR
Smart Scan
Smart Scan!
SBR/MBR
IORM
Dont be afraid
Why IORM?
Many databases
Different types of users
Different workloads
Different SLAs
Over-provision storage ?
IORM
Some basics
Resource consumer groups map sessions by workload
Combo of consumer groups and session mappings = resource
plan
Consumer groups assigned to categories key for IORM
An Exadata IORM plan is based on a database plan + a category
plan
Storage Indexes
Storage indexes <> normal indexes. Not at all
Goal: Eliminate unnecessary IO
Not by directing you specifically to table rows/blocks, but
By telling you with absolute certainty where not to look
Storage Indexes
Data stored in ASM Allocation Unit
Each 4M AU comprised of four 1MB storage regions
Storage regions track high and low values for columns in region
indexes
Region indexes are your storage indexes
Storage Indexes
When blocks access via Smart Scan, Exadata automatically
tracks high and low values in region index
When queries access blocks, Exadata cellsrv checks these
region indexes to see if any rows are contained in the storage
region if not, IO to storage region is skipped