Performance Tuning Apex Applications

81 Pages·2010·4.05 MB·English

by  Scott Spendolini

Performance Tuning
Apex Applications
Doug Gault
M B
Y ACKGROUND
•
Doug Gault
•
[email protected]
•
Using Oracle since 1988
•
Versions 5.1b, 6, 7, 8, 9, 10, 11
•
Focused on Web Technologies
•
OWA, ‘PSP’, Web DB, HTML-DB, APEX
•
Ex-Hotsos Employee of 5 years
•
Product Development Director - APEX Applications
•
2004 through 2008
•
Commercial Applications written in APEX
•
Joined Sumner Technologies January 2009
•
Co-Founded Sumneva January 2010
2
Copyright © 2010 Sumneva - All Rights Reserved - http://sumneva.com - [email protected]
A
GENDA
•
Introduction - Knowledge is Power
•
Coding Best Practices ... Get Started Right
•
Monitoring the Performance of Your Application
•
Tools Available for Diagnosis
3
Copyright © 2010 Sumneva - All Rights Reserved - http://sumneva.com - [email protected]
Introduction:
Knowledge is Power
4
Copyright © 2010 Sumneva - All Rights Reserved - http://sumneva.com - [email protected]
W D P , K P ...
HEN EALING WITH ERFORMANCE NOWLEDGE IS OWER
•
Know the Architecture
•
Know the Intended End User
•
Know the Expectations
•
Know the Application’s Purpose
5
Copyright © 2010 Sumneva - All Rights Reserved - http://sumneva.com - [email protected]
Know Your Architecture
6
Copyright © 2010 Sumneva - All Rights Reserved - http://sumneva.com - [email protected]
L A
OGICAL RCHITECTURE
•
APEX is a metadata-based environment
•
No need to write code to instantiate an APEX component
•
Rather you specify options with Wizards or the Application Builder
•
“Metadata-based” does not imply limitations on
complexity
•
APEX’s development environment is quite extensible
•
Can add calls to PL/SQL almost everywhere
•
Which can in turn, call other languages
•
APEX is built in APEX
7
Copyright © 2010 Sumneva - All Rights Reserved - http://sumneva.com - [email protected]
L A
OGICAL RCHITECTURE
•
Some benefits of a metadata-based framework:
•
No code is generated
•
Impossible to tune
•
Not extensible
•
Easy to transfer from one environment to another
•
Done without leaving the browser
•
Application Builder masks all complexity
•
User just sees screens and provides values
•
You can incorporate APEX metadata in your applications
8
Copyright © 2010 Sumneva - All Rights Reserved - http://sumneva.com - [email protected]
APEX S
CHEMAS
•
APEX is comprised of three schemas:
All APEX metadata is
APEX_030200
stored here
Any uploaded files end
FLOWS_FILES
up here initially
All APEX page views
APEX_PUBLIC_USER*
connect as this schema
* When the EPG is used, ANONYMOUS will be the public APEX schema
9
Copyright © 2010 Sumneva - All Rights Reserved - http://sumneva.com - [email protected]
P A
HYSICAL RCHITECTURE
•
Despite its simplicity, the physical architecture of APEX
can be configured a number of different ways
•
Simple for development & testing
•
Everything on a single box
•
Sophisticated for production
•
Multiple HTTP Servers with a Load Balancer
•
SSL & ASO for end-to-end secure transactions
•
RAC at the Database tier for performance boosts
•
Data Guard for fault tolerance
10
Copyright © 2010 Sumneva - All Rights Reserved - http://sumneva.com - [email protected]