Measure plsql execution time

Hello dear teachers,
i would be gratful for advice.
I have materialized view that is refreshed with the dbms_mview procedure and it's scheduled through dbms_job.
How could i measure that refresh execution time so i can for example query one table and have in there when this job(refreshing) started , and when did it finish ?
I could do set timing on in sqlplus , but is there somthing like that in plsql and than insert that time in some table ?
i am on 9.2.0.7.

set serverout on
declare
start_time number;
elapsed number;
begin
select to_char(sysdate,'sssss') into start_time from dual;
-- put here your code
select to_char(sysdate,'sssss')-start_time into elapsed from dual;
dbms_output.put_line ('Elapsed='||elapsed);
end;
/You can use systimestamp to get a more precise result.
Max
[My Italian Oracle blog|http://oracleitalia.wordpress.com]

Similar Messages

Measure procedure execution time..

Hi,
Is there any possibility to measure how long each of a procedure in database take?? Is that possible for Oracle's V$ views or by performance report like AWR? On the other hand, is that possible to measure execution time for SQL statements, but without using "set timing on".
Best,
tutus

This is just an add-on to Satish's reply. You may want to chck this link to see how Profiler works,
http://www.oracle-base.com/articles/9i/DBMS_PROFILER.php
HTH
Aman....

How to measure fpga execution time

Howdy--
I'm hacking through my first FPGA project without yet having the hardware on hand, and I find I could answer a lot of my own questions if I could predict what the execution time (ticks, mSec, whatever) of bits of my code will be. Running FPGA VIs on the Dev Computer with built in tick counters does not seem to be the proper way to go. Is it possible to know the execution time of FPGA code before compiling and running it on the target?
If it matters to anyone, my context for the question is a situation where a 10 uSec loop is imposed by the sample time of my hardware (cRIO 9076, with a couple of 100 ks/S I/O cards), and I'm trying to figure out how much signal processing I can afford between samples.
Thanks everyone, and have a great day.
Solved!
Go to Solution.

bcro,
You can look into cycle accurate simulation, which would give you a better understanding of how your code will work. More information can be found here: http://zone.ni.com/devzone/cda/tut/p/id/12917
As a rough measure, you can estimate that simple functions will take one tick to execute. However, there is not list of what is and is not a simple function.
You could also try placing code inside a single cycle timed loop (SCTL), which would then guarantee that all of the code in the loop will execute in 1 tick. However, if you are doing a lot of operations or trying to acquire an analog input, this will fail compilation.
Drew T.
NIC AE Specialist

Measure command execution time

How can we measure that how much time has been taken by a command to complete. For instance if i 'm running a find / -name something ..
how can i find out for much time did this command run.

Try the time command. See man time.

Execution time of a flat-sequence

Hello there -
Is there any way to get a measurement of how long each part of
the flat sequence takes to execute? Anything like matlab's "tic" and "toc"
commands in labview? I have been playing with it for a while now and
have yet to discover if Labview has this functionality. Anyone know of
anything like this?
I currently have a VI that controls the realtime acquisition of a CCD camera via Firewire and a USB spectrometer. The VI collects data from each of these devices (triggered by an external source at 10Hz), and dumps them into a Matlab script which does analysis on the CCD image and spectrum. The bulk of the VI sits inside a while loop, which continues to run until the user presses the stop button. Inside this main loop is a flat-sequence. The sequence goes: ACQUIRE DATA ---> PROCESSING DATA ----> MATLAB SCRIPT ----> PLOTTING GRAPHS -----> OUTPUT DATA TO FILE.
The problem here is that the VI runs at 5Hz, while we are triggering it at 10Hz. Originally, it was my thought thought that the matlab algorithm was to blame, but I used the matlab commands "tic" and "toc" to determine that the matlab algorithm runs in 15-20ms. I did this by putting a "tic" command at the top of the matlab algorithm and a "toc" command at the bottom. The problem, as I have now discovered is that the rest of the labview code takes ~180ms to execute. (This was discovered by putting the "tic" at the bottom of the program, and the "toc" at the top of the program, thereby measuring the execution time of everything except the matlab algorithm). Each time a trigger signal from the external source comes in, it starts the flat-sequence structure (which takes ~190ms), and then waits for another trigger signal, always missing every second signal. My eventual goal is to reduce the bloat, and get the algorithm down to less than 100ms, so that I can run the VI and acquire data at 10Hz rather than 5Hz. If anyone can offer some help with this, it would be much appreciated!
Eric
P.S. - I have attached a copy of the VI that I am working on, but unfortunately, it most likely will not run on your computer....the VI will not run unless it is connected to a triggered spectrometer and CCD camera....but I have attached it anyways incase anyone who can help might want to take a look.
Attachments:
RTSpider.vi ‏376 KB

can we divide the program into 2 parts and use background process for acquisition and front end process for analysis?
I mean, create 2 VIs from the present VI and then launch the acquisition program dynamically as a background process and fire events in Main VI from acquisition VI and process it. not sure how much it is going to reduce. lets give a try....
Anil Punnam
CLD
LV 2012, TestStand 4.2..........

Execution time continues to increase while vi is running

I started with a vi which reads data from a WII remote (wiimote). The code works. I want to convert the acceleration data to velocity and displacement by numerical integration. Accurate conversion requires a measure of execution time. The vi correctly returns 9-11 ms when it first starts, however the measured intervals continue to increase in lenght as the vi runs. The measured interval goes from 10 ms to 80 ms after about 1 hour. I used a tick counter to measure the loop execution time. Any suggestions?
Attachments:
Simple Event Callback Roll Pitch. timed eventvi.vi ‏19 KB

Can you do some profiling to see which subVI could be the problem?
If you look at the task manager, how is the momery use over time?
Your timing systems seems flawed, because the execution of the first tick cound is poorly defined with respect to the rest of the code.
Some typical things to look out for.
growing arrays in shift registers
constantly opening references without ever closing them.
LabVIEW Champion . Do more with less code and in less time .

Execution time too low

I was trying to measure the execution time. The rate is 1KS/s per channel and the samples to read is 100 per channel in a for loop of 10. The time should be around 1000ms, but it's only 500-600ms. And when I changed the rate/numbers of samples, the execution time doesn't change..... how could this happen?
Solved!
Go to Solution.
Attachments:
trial 6.vi ‏19 KB

JudeLi wrote:
I've tried to drag the clear task out of the loop but every time I did it, it ended up in a broken wire saying that the soure is a 1-D array of DAQmx event and the type of sink is DAQmx event.....
You can right-click on the output tunnel and tell it to not auto index. But even better would be to use shift registers just in case you tell that FOR loop to run 0 times.
There are only two ways to tell somebody thanks: Kudos and Marked Solutions
Unofficial Forum Rules and Guidelines
Attachments:
trial 6.vi ‏13 KB

LabVIEW2012 has long execution time to write string than LabVIEW2011 on XP SP3

in for loop, each execution will output string and display it on front panel by value property.
But after upgrade to LabVIEW 2012, the execution time doubled on Chinese XP OS, I really want to know this difference between LabVIEW 2011 & LabVIEW 2012, pls advice.
"I think therefore I am"

This is no way to measure the execution time. Your parallel while loop spins as fast as the computer allows, consuming all CPU it can get in the process, and starving everything else. Your code is highly flawed!
Eli: actually I add 10milliseconds delay inside both for and while loop.
In addition, get date/time in seconds is also a relatively expensive function, not to mention all these local variables! Your benchmark is completely meaningless! All it does is slow down your regular code, nothing else. How do you know in what order things start? Where is the "start time" initilized (where is the terminal?!)
Eli: I am using the states machine, and set the "start time" during the program initialization, then calculate "test time"in next case (running block).
A proper benchmark uses a three-frame flat sequence with to high resolution relative seconds timers, on in each outer frame and the code to be benchmarked in the inner frame. (here is an example). The difference between the two timers is the exection time of the inner code in seconds. Make sure to only have wires in the benchmarking code. All controls and indicators belong outside the sequence. Also make sure that no other code can run in parallel to the sequence.
Use this and you'll be surprise how fast your code actually runs.
Then you should also disabele debugging.
Please attach your actual code (including the subVI) so we can see what else you are doing wrong.
Eli: if possible, give me your mail address, then I can sent more actual code to you separately.
"I think therefore I am"

OSB: reporting via service callout & reporting execution times

Assume I made a common local service for a general report action and it's called from all inbound proxy services. At the moment all I see is in the report database is: inbound service uri: LocalProxy and inbound service name: <my local report service name>. How can I log the original service instead which was called?
An other question: is it possible to report the execution time of the service call into the database as well? I'd prefer having two measures: service execution time from the inbound proxy service until it leaves the ESB with the response; and the called business service execution time.

>
How can I log the original service instead which was called?
>
It was discussed here before: Re: How to call a OSB proxy service from a different OSB process?
Search forum to get more inputs.
>
An other question: is it possible to report the execution time of the service call into the database as well? I'd prefer having two measures: service execution time from the inbound proxy service until it leaves the ESB with the response; and the called business service execution time.
>
OSB out-of-box monitoring capabilities are not enough?
http://download.oracle.com/docs/cd/E13159_01/osb/docs10gr3/operations/monitoring.html
If you want to log execution time of every single call, try searching forum again.

How could I measure the excution time of the VI

hiii
I need to measure the execution time or the elapsed time of the prog in LabVIEW , I know that this time is very small but I need to calculate how much it is?
are there a suitable vi to do this in lib of LabVIEW or we must build it?

There is an integrated tool, the VI profiler, Darren presents it here.
You can also find usefull info if you go on the LabVIEW community and search for "VI profiler" or "performance", you'll find all sorts of articles, blogs that can help you : https://decibel.ni.com/content/search.jspa?peopleEnabled=true&userID=&containerType=&container=&spot...
Hope this helps
When my feet touch the ground each morning the devil thinks "bloody hell... He's up again!"

Java statements execution time

How to measure the execution time of a java statement in a repeatable and consistent manner.
We are measuring time by executing the interesting Java code 200 000 000 times in a loop and measuring the execution time of the whole loop by calling System.currentTimeMillis() before and after. However, we observe that the time needed to execute the loop is not constant. It varies both if the same measurement code is executed several times in an outer loop and if code before the timer loop is modified. Because of these inconsistencies we find it difficult to measure the execution time.

You must also understand that there will be no consistent way to measure time from within the program itself, because things such as process swapping, memory cleanup, bottom halves, interrupts, and all sorts of kernel tasks (regardless of the kernel -win or linux), are happening at intervals based on a number of system timers. Because all of these are completely transparent to a java process, it will not be able to decide reliably how long it takes to execute a method.
Somebody suggested useing a java profiling tool such as JProbe. This is a good suggestion.
If you want a reasonable estimate, execute your method several thousand times, collect the run time data, and take the mean. You can even use statistical methods to come up with a confidence interval and standard deviation, if you are that interested :) Hope this helps,
-Joe

Tool for measuring execution time?

Hi,
i'm trying to measure the time of some determined methods in my app.
I've tried System.currentMillis(), but i don't get the accuracy i need (System.nanoTime() - from 1.5.0 sdk won't help me neihter).
Does anyone know a simple java tool that i can use to do this ???
I thought about optimized (borland), but i just don't have it :-( also i don't know if it ease to use (and i need this measuring as soon as possible).
Thanks for any sugestion,
ltcmelo

<<In Windows at least the resolution of System.currentTimeMillis() seems to be 10ms.
If the operation that takes 9 ms is called a thousand times, and the one that takes 5 ms is called 20
million times, and the one that takes 1 �s is called 200 million times, all will be fast to measure,
all will come in at zero ms by currentTimeMillis(). It would be useful to know the respective execution times of each method.>>
This is not correct. Windows does have 10 ms. granularity, however if you average many measurements this limitation disappears.
For example let's say that a particular method takes 5 ms. on average and we take 10 measurements. You claim that the 10 measurements will all be 0, whereas the actual measurements will either be 0 or 10 depending on how close the clock was to ticking when currentTimeMillis() was called. For example the 10 measurements might look like 0, 0, 10, 0, 10, 0, 0, 10, 10, 0. If you take the average of these numbers you get quite good accuracy (i.e. 50/10=5 ms. the actual time we said the method took). In principle the average should even get you sub-ms. accuracy.
Try it with jamon (http://www.jamonapi.com). JAMon calculates averages and so gets around the windows limitation. If you are coding a web app then jamon has a report page that displays all the results (hits, average time, totals time, min time, max time, ...). If not then you can get the raw data and display it as you like.
One question for the original poster. Why do you think you need sub-millisecond timings? If you are coding a business app IO tends to be the bottleneck and much greater than sub-millisecond.
Steve - http://www.jamonapi.com - a fast, free monitoring tool that is suitable for production applications.

Measuring execution time

Hi, I had written a program a while back which was
simply loading in an xml file, parsing out a few
tags, and then writing back to the same file. I
thought of a way the parsing could be made more
efficient, and it certainly seems to be running faster,
however I am looking for suggestions on how I could
prove this?
Basically I am looking for a tool that could monitor
the length of time taken for the program to finish, so
I could do this using both versions of the program using
a set data set and compare the results.
Thanks in advance for any ideas/suggestions :)

It's fun putting subject lines in the search box
http://search.java.sun.com/search/java/index.jsp?and=ex
cution+time&phr=&qt=�=&field=title&since=&nh=10&col=
avaforums&rf=0&Search.x=19&Search.y=7Why limit yourself to 19 results, though? Search all the forums for "execution time" and you get 55,061 results. "Performance testing" yields 36,651 hits. I guess there's an outside chance one of those threads might be helpful, eh?

How to get the execution time of a Discoverer Report from qpp_stats table

Hello
by reading some threads on this forum I became aware of the information stored in eul5_qpp_stats table. I would like to know if I can use this table to determine the execution time of a worksheet. In particular it looks like the field qs_act_elap_time stores the actual elapsed time of each execution of specific worksheet: am I correct? If so, how is this value computed? What's the unit of measure? I assume it's seconds, but then I've seen that sometimes I get numbers with decimals.
For example I ran a worksheet and it took more than an hour to run, and the value I get in the qs_act_elap_time column is 2218.313.
Assuming the unit of measure was seconds than it would mean approx 37 mins. Is that the actual execution time of the query on the database? I guess the actual execution time on my Discoverer client was longer since some calculations were performed at the client level and not on the database.
I would really appreciate if you could shed some light on this topic.
Thanks and regards
Giovanni

Thanks a lot Rod for your prompt reply.
I agree with you about the accuracy of the data. Are you aware of any other way to track the execution times of Discoverer reports?
Thanks
Giovanni

How to measure mapping execution speed

Hi,
currently i'm trying to measure performance differences between Interface Mappings which contain one single Message Mapping and Interface Mappings which contain 2 or 3 Message Mappings.
I already tried to do this with RWB and Performance-Monitoring. But Performance Monitoring shows the processing time through the whole XI, and not only Mapping execution time. So it is difficult to get a clean measuring there, without influences from queueing and so on.
Test Tab on Integration Builder has a too big step (one second). Mapping execution time is slower.
Do you have any ideas to measure this?
Or do you have experience with performance differences between those two kinds of Interface Mappings?
regards,
ms
P.S. i'm using XI 3.0

Hi, Manuel:
For the two scenarios you want to compare performance, trigger them separately.
You take following steps to take measurement for those two scenarios:
Go to SXMB_MONI, find the message, go to pipeline step after your "Request Message Mapping"
e.g. you can select "Technical Routing" step, expand it, -> SOAP Header -> Performance Header:
You will see the start time stamp for each steps executed up to current step.
Locate your mapping programs, get the begin time stamp and end time stamp, then you will know the how long the mapping program take.
For the scenario that you have several mapping programs, make sure you get begin timestamp for the first mapping program and end timestamp for last mapping program, the difference is the time for you few mapping program take.
Hope this helps.
Liang
Edited by: Liang Ji on Mar 29, 2008 5:42 AM

Measure plsql execution time

Similar Messages

Maybe you are looking for