state.cooprotector.com | ||
Simple .NET/ASP.NET PDF document editor web control SDKThe tkprof utility takes a sql_trace trace file as input and produces a text-based report file as output. It s a simple utility that summarizes a large set of detailed information in a given trace file so that it can be understood for performance tuning. This section explains briefly how to use this very useful utility. In its simplest form, tkprof can be invoked as shown here: tkprof <trace-file-name> <report-file-name> To illustrate the joint use of tkprof and sql_trace, we ll set up a simple example. Specifically, we ll trace the query used previously in the autotrace example and generate a report from the resulting trace file. First, we log into SQL*Plus as the intended user, and then execute the following code: SQL> select c.value || '\ORA' || to_char(a.spid,'fm00000') || '.trc' 2 from v$process a, v$session b, v$parameter c 3 where a.addr = b.paddr 4 and b.audsid = userenv('sessionid') 5 and c.name = 'user_dump_dest'; C.VALUE||'\ORA'||TO_CHAR(A.SPID,'FM00000')||'.TRC' ---------------------------------------------------------------------------------------------------------------------------------C:\oracle\admin\oratest\udump\ORA01528.trc SQL> alter session set timed_statistics=true; Session altered. generate barcode excel vba, microsoft excel barcode generator software, barcode in microsoft excel 2010, barcode font excel 2013 free, barcode font microsoft excel 2007, free barcode font excel 2010, barcode add in excel, how to print barcode labels with excel data, barcode font excel 2003, barcode add in for excel 2007,SQL> alter session set sql_trace=true; Session altered. SQL> select * from emp, dept 2 where emp.deptno=dept.deptno; SQL> alter session set sql_trace=false; SQL> exit Now we simply format our trace file from the command line using tkprof, as follows: C:\oracle\admin\oratest\udump>tkprof ORA01528.TRC tkprof_rep1.txt We can open the tkprof_rep1.txt file and view the report. I don t intend to discuss the output in detail here, but briefly, at the top of the report we should see the actual SQL statement issued. Next, we get the execution report for the statement. call count ------- -----Parse 1 Execute 1 Fetch 2 ------- -----total 4 cpu elapsed disk query current rows -------- ---------- ---------- ---------- --------0.01 0.02 0 0 0 0 0.00 0.00 0 0 0 0 0.00 0.00 0 2 8 14 -------- ---------- ---------- ---------- --------0.01 0.02 0 2 8 14 Whenever a copy of a pointer to an interface is copied, the programmer is required to invoke the AddRef method of the IUnknown interface (every interface inherits from IUnknown), and when the pointer is no longer required, the Release method should be called to decrement the counter inside the component When the counter reaches zero, the component is automatically freed This strategy of memory management, though more automatic than the traditional malloc/free handling of the heap, has proven to be error prone, because programmers often forget to increment the counter when pointers are copied (risk of dangling pointers) or decrement when a pointer is no longer needed (risk of memory wasted in garbage). Figure 3-14. An excerpt from the Trace output report showing the relative rendered and view state sizes of the controls on the page Any element in the markup that doesn t have the runat=server attribute added to its declaration will be flattened in the control tree. That is to say, not all elements in the markup become objects in the control tree. To create an object for each element would be horribly wasteful and inefficient. The whole point of having an element represented as an object in the control tree is to interact with it programmatically. If there s no need to deal with it programmatically, then there s no need to incur the overhead of allocating on object to the managed heap to represent the element. Consider the previous example of our markup (see WebForm1.aspx in the Web03 project): <HTML> <HEAD><title>WebForm1</title></HEAD> <body> <form id="Form1" method="post" runat="server"> <asp:Label id="Label3 runat="server">User Name</asp:Label> <asp:TextBox id="TextBox1" runat="server" /> <asp:Label id="Label2" runat="server">Password</asp:Label> <asp:TextBox id="TextBox3" runat="server" /> <asp:Button id="Button1" runat="server" Text="Login" /> <asp:Label id="lblOutput" runat="server" />j </form> </body> </HTML> This report illustrates the three different phases of Oracle SQL processing: parse, execute, and fetch. For each processing phase, we see the following: The number of times that phase occurred The CPU time elapsed for the phase The real-world time that elapsed The number of physical I/O operations that took place on the disk The number of blocks processed in consistent-read mode The number of blocks read in current mode (reads that occur when the data is changed by an external process during the execution of the statement) The number of blocks that were affected by the statement
| ||