Cary,
In a TKPROF report, there is a small table at the top. It includes a column
for CPU time and another for Elapsed Time.
Suppose the total line shows CPU = 3.00 and elapsed = 5.00. You would think
that the two seconds difference would be for waits, but that doesn't seem to
be true.
Since
Greg Moore wrote:
Cary,
In a TKPROF report, there is a small table at the top. It includes a column
for CPU time and another for Elapsed Time.
Suppose the total line shows CPU = 3.00 and elapsed = 5.00. You would think
that the two seconds difference would be for waits, but that
To: Multiple recipients of list ORACLE-L
[EMAIL PROTECTED]
otsos.comcc:
Sent by: Subject: RE: I/O EVENTS
Hi Cary,
I also have a same problem but could not solve it yet
I have two m/cs and with identical DB layout etc and
running the
same pro*C code under same data volume.The top waits
are as follows.
1.oracle-8.0.5 ( 2 processor/RAM 512 MB)
Total run time 45 mins
Event
the latency per call on the SQL*Net message
from client event looked suspiciously LAN-like
(order of 10ms), not IPC-like (order of 1ms or less)
Oracle Kernel EventDurationCallsAvg
-- -- --
SQL*Net
0.010340 second ~ 10/1,000 second = 10ms (= 1/100 second)
If the number had been on the order of 0.001 (1ms) or less, it would've
looked more IPC-like.
Cary Millsap
Hotsos Enterprises, Ltd.
[EMAIL PROTECTED]
http://www.hotsos.com
-Original Message-
Sent: Wednesday, May 22, 2002 7:38
So just looking at v$system_event is dangerous.
Looking v$system_event and v$sysstat
is much better but still not perfect. The third
way is ... (mail me ;-))
Anjo,
Jared has an even hand on the tiller. Go ahead an post an informative
example of how the v$ views don't allow you to
PROTECTED]
05/21/2002 12:13 AM
Please respond to ORACLE-L
To: Multiple recipients of list ORACLE-L [EMAIL PROTECTED]
cc:
Subject:Re: I/O EVENTS
So just looking at v$system_event is dangerous.
Looking v$system_event and v$sysstat
is much better but still
I have an example for you (Anjo, I hope you won't mind). A prospect we
visited once upon a time had been fighting a performance problem with an
Oracle Payroll program. They knew what their problem was: very
clearly, v$system_event was telling them that their overwhelmingly
dominant system
Cary,
This is greatness.
Jack
--- Cary Millsap [EMAIL PROTECTED] wrote:
I have an example for you (Anjo, I hope you won't
mind). A prospect we
visited once upon a time had been fighting a
performance problem with an
Oracle Payroll program. They knew what their
problem was: very
Hi Greg,
Maybe not one, but what about two? At the same time v$system_event is
checked a couple of times, so you can see a time slice,
v$sysstat can be
checked, focusing on CPU used by this session, parse time cpu
and recursive
cpu usage. One view gives wait time, one gives CPU time.
Download the YAPP paper ;-)
Anjo.
John Kanagaraj wrote:
Greg,
Can I assume a i/o bottleneck from the following
select * from v$system_event
order by TIME_WAITED;
No. Wait events may only make up a small amount of
processing that Oracle
is doing for you.
Hmm I
...
Can I assume a i/o bottleneck from the following
statistics as most of the i/o events are having high
wait time.
select * from v$system_event
order by TIME_WAITED;
The last few entries are as follows.
EVENT TOTAL_WAITS
TOTAL_TIMEOUTS TIME_WAITED
Hi
Can anybody explain the events like
SQL*Net message from client,rdbms ipc message
PX Idle Wait ,slave wait ...
Can I assume a i/o bottleneck from the following
statistics as most of the i/o events are having high
wait time.
select * from v$system_event
order by TIME_WAITED;
The last few
Can I assume a i/o bottleneck from the following
select * from v$system_event
order by TIME_WAITED;
No. Wait events may only make up a small amount of processing that Oracle
is doing for you.
--
Please see the official ORACLE-L FAQ: http://www.orafaq.com
--
Author: Greg Moore
INET:
Wait ,slave wait ...
Can I assume a i/o bottleneck from the following
statistics as most of the i/o events are having high
wait time.
select * from v$system_event
order by TIME_WAITED;
The last few entries are as follows.
EVENT TOTAL_WAITS
TOTAL_TIMEOUTS TIME_WAITED
Greg,
Can I assume a i/o bottleneck from the following
select * from v$system_event
order by TIME_WAITED;
No. Wait events may only make up a small amount of
processing that Oracle
is doing for you.
Hmm I wouldn't think so. If there were just _one_ overall view that I
could
John,
Hmm I wouldn't think so. If there were just _one_ overall view that I
could check to determine an Oracle bottleneck, it would be this view.
Maybe not one, but what about two? At the same time v$system_event is
checked a couple of times, so you can see a time slice, v$sysstat can be
18 matches
Mail list logo