> Scott,> > How about:> > select dbms_utility.get_time from dual?> > > > function get_time return number;> -- Find out the current time in 100th's of a second.> -- Output argukments:> -- get_time> -- The time is the number of 100th's of a second from some> -- arbitrary epoch.> > > > -----Original Message-----> From: oracle-l-bounce_at_freelists.org> [mailto:oracle-l-bounce_at_freelists.org] On Behalf Of > scott.hutchinson_at_interact-analysis.com> Sent: Friday, September 30, 2005 10:31 AM> To: oracle-l_at_freelists.org> Subject: Millisecond timer in PL/SQL> > All,> > I'm looking for a way to measure the elapsed time (in milliseconds) of

> executing a bunch of functions within a PL/SQL package. I've written > a "timer"> function that records this by using SYSTIMESTAMP, however is causes > the sessions to spend a significant amount of time waiting on "cache > buffers> > chains".> > Coding "w_date := SYSTIMESTAMP;" will result in a recursive "SELECT > SYSTIMESTAMP FROM DUAL", and this is the sql being executed by > sessions waiting on this latch (from v$session_wait and v$sqlarea).> > Does anyone have suggestions for ways that I can improve this?> > I have 50 concurrent sessions (batch jobs) running this, and each will