SIG Wed 1345 Oracle 12c Database Performance and Recomendations PDF
SIG Wed 1345 Oracle 12c Database Performance and Recomendations PDF
Recommendations
Staying current with Oracle releases, Linux support packs, z/VM releases, hardware provides
some of the greatest non programmable performance gains as well as security compliance.
“Fit for Purpose” - databases and virtualization workloads vs. highly parallelized workloads.
– Oracle workloads gain high cpu utilizations and availability.
– System z processors have high clock speeds & cache
Oracle 12.1.0.1
Running Parallel Processes: 32
real 0m10.12s
user 0m0.16s
sys 0m0.14s
Embedded Function Call was being called multiple times per row…
– Modified Index to be more compact – PCTFREE 0 (columns were non update)
– Consolidated 2 sql checks to 1 to help reduce contention
– Reduced cpu consumption by 41% with just these 2 changes
Linux Large Pages recommended for Large databases with SGA > 10GB
with many user sessions, for both memory stability and performance (10%)
- Team started with 200 banking transactions per second (tps) on 2 IFLs
- 15.3% improvement with 12c from 9685 to 11676 banking transactions
per second, after upgrade to Oracle 12c (no other changes made).
- Reduced “concurrency” observed from 11.2.0.4 to 12.1.0.1
- Target tps was 10,000 tps -> achieved 12739 with 12 IFLs
Application users do not have access to other Pluggable databases in the CDB.
To change a parameter for all containers in the CDB including spfile you can run:
DB Name & Test 10 Total Trans User avg Sys avg I/O wait
Minutes (swingbench) utilization % utilization % avg %
test5_1_pdb +
test5_2_pdb 3,658,385 88.7 5.2 4.8
test3 + test4 (non
pluggable) 3,647,106 89.9 5.4 2.8
Linux out of memory killer (OOM) can kill any non root Linux process, sometimes the ASM
Instance processes can get killed.
Linux out of memory killer (OOM) can kill any non root Linux process, a lot times it’s the ASM
Instance processes can get killed.
FlexASM allows for a database instance using ASM – to be relocated to another ASM
Instance in the cluster.
19 © 2014 IBM Corporation
Oracle CPU Improvements (11.2.0.2 -> 11.2.0.3)
Oracle’s VKTM process uses slightly less CPU minutes
– (about 0.08 vs. 0.09 with 11.2.0.2)
– DB installed with all options : (java, xml, Text, spatial, APEX, etc ....... )
The "gettimeofday" function is called 1500 times every 15 seconds.
© 2014 IBM Corporation
20
Changing the database blocksize in a RAC environment
Impact in %
4% 0%
-5%
2% -10%
-15%
0% -20%
-2% 1 -25%
-30%
-4% -35%
-40%
-6% -45%
-50%
-8%
Estd Interconnect traffic (KB)
transactional throughput GCS/GES messages sent/received
wait class: Cluster Global Cache blocks served/received
wait class: Commit CR Blocks recv
Comparing environment using 4KB database blocks instead of 8KB
– improves the throughput about 4%
– contention based on cluster events is reduced by more than 4%
Cluster events
– Locking: one node has to wait until the other node releases a lock, lock size is database page!
– Waits for datablocks, smaller blocks reduce the load on the Interconnect approximately by the half
exec DBMS_STATS.GATHER_SYSTEM_STATS('NOWORKLOAD');
z9:
SNAME PNAME PVAL1
------------------------------ ------------------------------ ----------
SYSSTATS_MAIN CPUSPEEDNW 533
Linux bogomips per cpu: 6510.00
z196:
SNAME PNAME PVAL1
------------------------------ ------------------------------ ----------
SYSSTATS_MAIN CPUSPEEDNW 2335
Linux bogomips per cpu: 14367.00
zEC12:
SNAME PNAME PVAL1
------------------------------ ------------------------------ ----------
SYSSTATS_MAIN CPUSPEEDNW 2613
Linux bogomips per cpu: 18115.00
Reduces Unnecessary
Statistics Collection
Oracle10gR2+ best to let Oracle automatically set the optimal log_buffer size. (i.e. leave unset
in the init.ora).
Check AWR Report - ideally log switches every 15 – 20 minutes.
If log switches more frequent you should increase size of logs.
If using fast_start_mttr_target then can use:
select optimal_logfile_size from v$instance_recovery;
Data DG FRA DG
ERP DB
BI DB
HR DB
select window_name,RESOURCE_PLAN
from DBA_SCHEDULER_WINDOWS;
WINDOW_NAME RESOURCE_PLAN
------------------------------ ------------------------------
MONDAY_WINDOW DEFAULT_MAINTENANCE_PLAN
WINDOW_NAME RESOURCE_PLAN
------------------------------ ------------------------------
MONDAY_WINDOW © 2014 IBM Corporation
29
Performance Management Strategies – Linux on System z
Performance problems usually come in 2 main areas :
– Database wide problems (problems which affect all users and sql queries)
– Query specific problems (problems which affect only one, or few, queries)
Query specific issues – many of the Oracle supplied query diagnostic tools work well.
Oracle Enterprise Manager 12c (12.1.0.2 / 12.1.0.3 contains capabilities for 12c databases)
– Linux on System z agents are deployed from centralized OMS server.
31 Source: Getting Optimal Performance from Oracle E-Business Suite - Samer Barakat OOW 2013 © 2014 IBM Corporation
Oracle Performance Diagnostics
Snapshots (take snaps before & after test):
– exec DBMS_WORKLOAD_REPOSITORY.CREATE_SNAPSHOT;
Summarized
Errors
Performance
Reports
Redbooks:
sg248159 - 12c Experiences http://www.redbooks.ibm.com/redpieces/abstracts/sg248159.html?Open
sg248104 - 11gR2 Experiences http://www.redbooks.ibm.com/abstracts/sg248104.html?Open