Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Mailing Lists -> Oracle-L -> Re: CPU_TIME > ELAPSED_TIME

Re: CPU_TIME > ELAPSED_TIME

From: Eagle Fan <eagle.f_at_gmail.com>
Date: Wed, 24 Oct 2007 13:59:10 +0800
Message-ID: <4415a5ed0710232259p723917b8o91036551d7b6a999@mail.gmail.com>


Do you mean cpu cycle?

I have the book, will check it later

Thanks

On 10/24/07, Daniel Fink <daniel.fink_at_optimaldba.com> wrote:
>
> Elapsed time and CPU time are not measured the same. Elapsed time is a
> stop watch. CPU time is a calendar with the rule that you get credit for
> the full day if you are present when the day starts.
>
> You could be on the job for 10 minutes...but get credit for 24 hours if
> those 10 minutes started precisely at midnight. You could also be on the
> job for 23 hours and 50 minutes...and get no credit for hours because
> you were not on the job when the day started.
>
> Cary Millsap covers this in his book "Optimizing Oracle Performance".
>
> --
> Daniel Fink
>
> Oracle Performance, Diagnosis and Training
>
> OptimalDBA http://www.optimaldba.com
> Oracle Blog http://optimaldba.blogspot.com
>
>
>
> Eagle Fan wrote:
> > yes, I also thought about this possibility before.
> >
> > But this query is very simple, it's doing index unique scan on PK
> > index. buffer gets per execution is only 3.
> >
> > I can't image it run on multiple CPU at one time.
> >
> > What do you think?
>
>
>

-- 
Eagle Fan

Oracle DBA

--
http://www.freelists.org/webpage/oracle-l
Received on Wed Oct 24 2007 - 00:59:10 CDT

Original text of this message

HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US