Performance Instrumentation for PL/SQL: When, Why, How
•Télécharger en tant que PPT, PDF•
12 j'aime•3,160 vues
Performance instrumentation is a little extra code that developers put into their PL/SQL applications that tells everyone—owners, users, system managers, and the software developers themselves—exactly where your software is spending your time. With it, managing performance is a snap. Good instrumentation makes it so normal people, not just specialists, can diagnose and solve performance problems quickly and permanently, often before your users even sense something is wrong. However, without good time-based performance instrumentation, managing performance becomes nightmarishly complex and expensive. With as little as two lines of code you will be able to monitor specific tasks in your application and make one of the most difficult steps of implementing response-time based problem diagnosis (Method R) into one of the easiest. In addition, these techniques will enable you to correlate database statistics back to business tasks and help discover those tasks that are heavy resource consumers. This presentation will provide examples of how to perform the instrumentation using Oracle's built-in packages and a free open source instrumentation package called the Instrumentation Library for Oracle (ILO). Its cost on every level is free, and the significant collateral benefits that can be achieved will make code instrumentation part of your coding standards.
![Your speaker… ,[object Object],[object Object],[object Object],[object Object],[object Object],[object Object]](data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7)
Recommandé
Contenu connexe
Tendances
Tendances (20)
En vedette
En vedette (20)
Similaire à Performance Instrumentation for PL/SQL: When, Why, How
Similaire à Performance Instrumentation for PL/SQL: When, Why, How (20)
Dernier
Dernier (20)
Performance Instrumentation for PL/SQL: When, Why, How
- 1. Performance Instrumentation for PL/SQL When, Why, How Karen Morton
- 27. TCO $$ Waste Labor $$ Hardware $$ Software $$
- 53. Day 1 Depart 7:40am Arrive 8:20am
- 58. Category Miles Elapsed Time (minutes) Neighborhood 1 3 Burke Centre Pkwy 2.5 8 Fairfax County Pkwy 6 12 I-66 2.5 8 Hwy 28 2 5 Westfields Blvd to Office 1.5 4 Total 15.5 40 minutes
- 62. Conclusion Leave earlier to allow for traffic fluctuations
- 67. Tracks and measures performance
- 73. What are the benefits of proper instrumentation?
- 76. This?
- 77. Or this?
- 78. This?
- 79. Or this?
- 82. How do I instrument my code?
- 86. Lets instance know which end users are on which connection
- 107. SELECT * FROM V$SERV_MOD_ACT_STATS when using serv_mod_act_stat_enable
- 108. Where should I place instrumentation?
- 115. PROCEDURE get_emp_simple_instr IS fnlist_stack fnlist_tab; lnlist_stack lnlist_tab; BEGIN DBMS_APPLICATION_INFO.set_module(module_name => 'Human Resources’,action_name => 'Get Employees'); SELECT first_name, last_name BULK COLLECT INTO fnlist_stack, lnlist_stack FROM employees; DBMS_APPLICATION_INFO.set_module(NULL, NULL); EXCEPTION WHEN OTHERS THEN DBMS_APPLICATION_INFO.set_module(NULL, NULL); DBMS_OUTPUT.PUT_LINE('get_emp_simple_instr => ERROR'); END get_emp_simple_instr;
- 116. 08:00:00 MODULE = ‘Human resources’ ACTION= ‘get employees’ 08:02:04 MODULE = null ACTION = null
- 117. PROCEDURE get_emp_jobs_instr_flawed IS jtlist_stack jtlist_tab; lnlist_stack lnlist_tab; BEGIN DBMS_APPLICATION_INFO.set_module(module_name => 'Human Resources', action_name => 'Get Employees and Jobs'); get_emp_simple_instr; SELECT last_name, job_title BULK COLLECT INTO lnlist_stack, jtlist_stack FROM employees e, jobs j WHERE e.job_id = j.job_id; DBMS_APPLICATION_INFO.set_module(NULL, NULL); EXCEPTION WHEN OTHERS THEN DBMS_APPLICATION_INFO.set_module(NULL, NULL); DBMS_OUTPUT.PUT_LINE('get_emp_jobs_instr_flawed => ERROR'); END get_emp_jobs_instr_bad;
- 118. 08:10:00 MODULE = ‘Human resources’ ACTION = ‘get employees and jobs’ 08:12:04 MODULE = null ACTION = null 08:10:01 MODULE = ‘Human resources’ ACTION = ‘get employees’ 08:13:32 <end>
- 121. PROCEDURE get_emp_instr_good IS fnlist_stack fnlist_tab; lnlist_stack lnlist_tab; preModuleName VARCHAR2(48) := NULL; preActionName VARCHAR2(32) := NULL; BEGIN DBMS_APPLICATION_INFO.read_module( module_name => preModuleName, action_name => preActionName); DBMS_APPLICATION_INFO.set_module( module_name => 'Human Resources', action_name => 'Get Employees'); SELECT first_name, last_name BULK COLLECT INTO fnlist_stack, lnlist_stack FROM employees; DBMS_APPLICATION_INFO.set_module( module_name => preModuleName, action_name => preActionName); EXCEPTION WHEN OTHERS THEN DBMS_OUTPUT.PUT_LINE('HR_Package.get_emp_instr_good ERROR'); DBMS_APPLICATION_INFO.set_module( module_name => preModuleName, action_name => preActionName); END get_emp_instr_good;
- 138. PROCEDURE get_emp_instr_better IS fnlist_stack fnlist_tab; lnlist_stack lnlist_tab; BEGIN ILO_TASK.BEGIN_TASK(module_name => 'Human Resources' ,action_name => 'Get Employees'); SELECT first_name, last_name BULK COLLECT INTO fnlist_stack, lnlist_stack FROM employees; ILO_TASK.END_TASK; EXCEPTION WHEN OTHERS THEN DBMS_OUTPUT.PUT_LINE('get_emp_instr_better ERROR'); ILO_TASK.END_TASK; END get_emp_instr_better;
- 162. Majority of time spent waiting for gc cr multi block request
- 163. Further drilldown showed one insert and one delete to be largest “R” contributors
- 164. Reviewed the insert statement which was actually inserting via a SELECT
- 165. 1) Noted excessive LIO 2) Plan showed use of full table scan
- 167. Added index on ts_row_seq
- 169. New response time 10.118 seconds
- 185. Questions & Answers
Notes de l'éditeur
- Course or presentation name © 2008 Method R Corp.
- Collect properly scoped , un-aggregated profile data for each task while the task is exhibiting the behavior you want to record Login Triggers Unique code changes
- Collect properly scoped , un-aggregated profile data for each task while the task is exhibiting the behavior you want to record Login Triggers Unique code changes
- … costs you money
- Your slow stuff will clog up even your fast stuff.
- “ Slow. Why?” Ok …What does “slow” mean?
- 129.98 seconds Why?
- 129.98 seconds (this is R data) Why? Where is the time spent? (we need profile data)
- Real-life performance instrumentation
- Real-life performance instrumentation
- Real-life performance instrumentation
- Test 1: I delivered the presentation to my cats. I used a stop watch to keep a running time My cats were thrilled to participate My test presentation was just short of 2 hours
- Emit a line-by-line execution of each step with a time stamp Available in any environment (e.g. development, production…) Always ready to be activated Easy to perform Light weight Uses built-in functionality as much as possible
- Enterprise Manager V$ views
- No idea of who are the clients Large amount of activity by unnamed modules and actions
- Know who the client is and be able to drilldown See specific module and action that are the “Top Consumers” Able to trace right from DBConsole and Grid Control
- Enterprise Manager V$ views
- Enterprise Manager V$ views
- Emit a line-by-line execution of each step with a time stamp Available in any environment (e.g. development, production…) Always ready to be activated Easy to perform Light weight Uses built-in functionality as much as possible
- Create a simple logon trigger to set CLIENT_IDENTIFIER CREATE OR REPLACE TRIGGER client_id_logon_trg AFTER LOGON ON DATABASE DECLARE my_service SYS.V_$SESSION.SERVICE_NAME%TYPE; my_clientid SYS.V_$SESSION.CLIENT_IDENTIFIER%TYPE; my_ip_address SYS.V_$SESSION.TERMINAL%TYPE; my_os_user SYS.V_$SESSION.OSUSER%TYPE; my_audsid SYS.V_$SESSION.AUDSID%TYPE; my_program SYS.V_$SESSION.PROGRAM%TYPE; CLIENT_ID_DELIM CHAR(1) := '~'; BEGIN IF USER NOT IN ('SYS') AND USER IS NOT NULL THEN my_clientid := SYS_CONTEXT('USERENV', 'CLIENT_IDENTIFIER'); IF my_clientid IS NULL THEN my_service := SYS_CONTEXT('USERENV', 'SERVICE_NAME'); my_ip_address := NVL(SYS_CONTEXT('USERENV', 'IP_ADDRESS') ,SYS_CONTEXT('USERENV', 'TERMINAL')); my_os_user := SYS_CONTEXT('USERENV', 'OS_USER'); my_audsid := TO_NUMBER(SYS_CONTEXT('USERENV', 'SESSIONID')); SELECT PROGRAM INTO my_program FROM SYS.V_$SESSION WHERE AUDSID = my_audsid AND ROWNUM = 1; DBMS_SESSION.SET_IDENTIFIER(my_os_user || CLIENT_ID_DELIM || my_ip_address || CLIENT_ID_DELIM || my_program || CLIENT_ID_DELIM || my_service); END IF; END IF; EXCEPTION WHEN OTHERS THEN DBMS_OUTPUT.PUT_LINE('client_id_logon_trg: Exception thrown'); END client_id_logon_trg;
- select column_name, table_name from dba_tab_cols where column_name like 'CLIENT_ID%' order by table_name COLUMN_NAME TABLE_NAME ------------------------------ ------------------------------ CLIENT_ID ALL_SCHEDULER_JOBS CLIENT_ID ALL_SCHEDULER_JOB_LOG CLIENT_ID ALL_SCHEDULER_WINDOW_LOG CLIENT_ID DBA_AUDIT_EXISTS CLIENT_ID DBA_AUDIT_OBJECT CLIENT_ID DBA_AUDIT_SESSION CLIENT_ID DBA_AUDIT_STATEMENT CLIENT_ID DBA_AUDIT_TRAIL CLIENT_ID DBA_COMMON_AUDIT_TRAIL CLIENT_ID DBA_FGA_AUDIT_TRAIL CLIENT_ID DBA_HIST_ACTIVE_SESS_HISTORY CLIENT_ID DBA_SCHEDULER_JOBS CLIENT_ID DBA_SCHEDULER_JOB_LOG CLIENT_ID DBA_SCHEDULER_WINDOW_LOG CLIENT_IDENTIFIER GLOBAL_CONTEXT CLIENT_ID GV_$ACTIVE_SESSION_HISTORY CLIENT_IDENTIFIER GV_$CLIENT_STATS CLIENT_IDENTIFIER GV_$GLOBALCONTEXT CLIENT_IDENTIFIER GV_$SESSION CLIENT_ID KET$_CLIENT_CONFIG CLIENT_ID KET$_CLIENT_TASKS CLIENT_IDENTIFIER MGMT_USER_CONTEXT CLIENT_ID SCHEDULER$_EVENT_LOG CLIENT_ID SCHEDULER$_JOB CLIENT_ID SCHEDULER$_LIGHTWEIGHT_JOB CLIENT_ID USER_AUDIT_OBJECT CLIENT_ID USER_AUDIT_SESSION CLIENT_ID USER_AUDIT_STATEMENT CLIENT_ID USER_AUDIT_TRAIL CLIENT_ID USER_SCHEDULER_JOBS CLIENT_ID USER_SCHEDULER_JOB_LOG CLIENT_ID V_$ACTIVE_SESSION_HISTORY CLIENT_IDENTIFIER V_$CLIENT_STATS CLIENT_IDENTIFIER V_$GLOBALCONTEXT CLIENT_IDENTIFIER V_$SESSION CLIENT_ID WRH$_ACTIVE_SESSION_HISTORY CLIENT_ID WRH$_ACTIVE_SESSION_HISTORY_BL 37 rows selected.
- Valid values of dest parameter are 1 = Trace file, 2 = Alert log, 3 = Both
- Monitor sessions by querying v$session
- Valid values of dest parameter are 1 = Trace file, 2 = Alert log, 3 = Both
- Monitor sessions by querying v$session
- http://sourceforge.net/projects/hotsos-ilo/
- Turning on trace is usually a run-time decision ( DBMS_MONITOR ) The developer will simply include BEGIN_TASK ILO calls that will check to see if someone has requested that a trace be initiated For development testing, the developer simply calls SET_MARK_ALL_TASKS_INTERESTING (TRUE, TRUE) to express their intent to trace Calls to this method will not typically be present in production code Except perhaps via a menu option (Help > Debug > Trace)