Execution time of IVI Steps

Hello,
We have made some benchmarks to decide the usefulness of TestStand IVI steps versus Labview ones with a PXI 4070 ( DMM ).
The Labview steps ( using also IVI access !!! ) are 30% faster than direct TestStand IVI steps.
May someone help us to understand such difference ?
Thanks a lot.

Oliver -
The TestStand step types have additional overhead because all the configuration information stored on the TestStand step must be evaluated and passed to the a VB component. Because the TestStand execution is multi-thread apartment and the VB component must be single thread apartment, some marshalling of data is necessary via COM. Lastly the VB component is not optimized as the IVI VIs that you are using. The TestStand IVI steps are not intended for speed, more easy of use. Hope this helps.
Scott Richardson
National Instruments

Similar Messages

How to extract execution time of a step

how to extract execution time of a step ?
This step calls another sequence, and
I want to know how long it take to execute that seqeuence.
I need this information during run time, not in the
report.
thanks.

Hi,
You could try.
Enable the Record Result for the step in question.
This will allow you to extract the TotalTime.
Then you could use the RemoveElements(Locals.ResultList,"[0]",1) - this assumes you have only logged one result. This is the same as not recording results for that step.
Otherwise you will have to workout the time yourself by calling the API Execution.SecondsExecuting() - API Execution.SecondsAtStart().
Regards
Ray Farmer
Regards
Ray Farmer

Measure waveform rise time with IVI step

I'm trying to simulate measurement of wafeform rise time through IVI step TS 4. How should I feed the Scope IVI step with waveform and then get the calculated rise time in simulation mode(I do not have the Scope yet.
Thank you.
Elik

Hi,
Thank you. So far it is simple, but I wonder if there is a way to feed to the IVI step through simulation waveform like square wave and different frequencies. I've tried using TDS 2000 series but I get the same data results.
I configure it as Normal Acquisition
Advance Tab Low Reference 10, Middle 50 and High 90.
Channels Tab, left the defaults except Maximum input frequency which I configure with variable
Trigger Tab Type Edge, Source Channel 1, Coupling DC, Slope Positive, Level 0.5
Extension Tab, Waveform Measurement.
I also set a step Read and set one of the channels to read Rise Time.
Although the waveform change The data from step results which I suppose give you the rise time stay the same.
Is there any way to change the waveform type and the rise time through the IVI step?
Thank you.
Elik

Can I reduce the execution time for a step in a TestStand ?

Hi,
I calculated the a single step execution time for TestStand Ver 2.0. It comes to around 20 milliseconds/step. Can I reduce this excution time ?
Are there any settings available for configuring execution time parameters except result logging and exception handlings to reduce the execution time ?

It's difficult to tell how you what time you are reporting for your step. Clearly we don't have control of the time it takes your code to execute. However, we are constantly working on reducing the overhead of calling the code. In addition, you don't mention the type of step you are calling. One way to have a common reference is to use the example \Examples\Benchmarks\Benchmarks.seq. Below have have posted the results of running this sequence with both tracing and result collection enabled and then disabled. I have a 700 MHz, 128 MB RAM, Dell PIII laptop. In this example there is no code within the code modules. You notice that calling a DLL has the least overhead with a minimum of 7.459 ms with tracing and results enabled and 0.092 ms with tracing and results disabled. Although not included below, if I enable results be disable tracing I get a minimum time of 0.201 ms, a 100x improvement on your time.
With Results and Tracing enabled.
7.578 milliseconds per step for CVI Standard Prototype - Object File
7.579 milliseconds per step for CVI Standard Prototype - DLL
7.459 milliseconds per step for DLL Flexible Prototype
8.589 milliseconds per step for DLL Flexible Prototype Numeric Limit
9.563 milliseconds per step for DLL Flexible Prototype Numeric Limit with Precondition
10.015 milliseconds per step for DLL Flexible Prototype Numeric Limit with Precondition and 4 Parameters
7.868 milliseconds per step for ActiveX Automation
8.892 milliseconds per step for LabVIEW Standard Prototype
With tracing and results disabled.
0.180 milliseconds per step for CVI Standard Prototype - Object File
0.182 milliseconds per step for CVI Standard Prototype - DLL
0.092 milliseconds per step for DLL Flexible Prototype
0.178 milliseconds per step for DLL Flexible Prototype Numeric Limit
0.277 milliseconds per step for DLL Flexible Prototype Numeric Limit with Precondition
0.400 milliseconds per step for DLL Flexible Prototype Numeric Limit with Precondition and 4 Parameters
0.270 milliseconds per step for ActiveX Automation
1.235 milliseconds per step for LabVIEW Standard Prototype

How to set execution time of the step with business days in the workflow

As we know, we can set how many days later the step should be execuated after previous step. now, the problem is how to set the business days (days except sunday and sataurday) for it. any one has good solution on it.

Hi Nick,
In order to find the Next working day you need to check for the Factory calendar days for eg, if a workitem has invoked today and if the Approver doesn't release the workitme for which u want to send a mail/reminder to the approver after say next 5or 6 working days, you need to create a function module.
For eg: In case of Purchase order, if the approver doesn't release the PO .
Create a Method saying "Next working day" , in which you will be passing the import parameters : PO, Factory calendar day and the sy-datum
and export parameter : date.
Create Input date and No of days as container elements of the Task and in the method create a Function module
In case of PO, consider the Factory calendar key from the T001W by joining the table EKPO there by passing the PO.
then pass the date, No of days(say 5 days) and the Factory calendar key to the "WDKAL_DATE_ADD_FKDAYS" , you will get the next working day of the employee.
Don't forget to check the Binding properly.
Do implement this logic and check the same.
Regards
Sharief

Long execution times for TestStand conditional statements

I have two test stations – one here, one at the factory in China that has been operating for about a year. The test program uses TestStand 3.1 and calls primarily dll's developed using CVI. Up until a couple months ago, both test stations performed in a similar manner, then the computer at the factory died and was replaced with a new, faster computer. Now the same test sequence at the factory take three times as long to execute (30 min at the facotry, 10min here).
I have recoded the execution time at various point during the execution, and have found that the extra times seems to be occurring during the evaluation of conditional statements in TestStand (i.e. for loops, if statements, case statements). For example, one particular ‘for’ evaluation takes 30 ms on the test station here, but takes 400 ms at the test station at the factory (note: this is just the evaluation of the for condition, not the execution of the steps contained within the for loop).
The actual dll calls seem to be slightly faster with the new computer.
Also the ‘Module Times’ reported don’t seem to match the actual time for the module for the computer at the factory. For example, for the following piece of TestStand code:
Label1
Subsequence Call
Label2
I record the execution time to the report text in both Label1 and Label2. Subtracting one from the other gives me about 18 seconds. However the ‘Module Time’ recorded for ‘Subsequence Call’ is only 3.43 seconds.
Any body have any ideas why the long execution time with the new computer? I always setup the computers in exactly the same way, but maybe there is a TestStand setting somewhere that I have missed? Keep in mind, both test stations are running exactly the same revision of code.

Got some more results from the factory this morning:
1) Task Manager shows that the TestExec.exe is the only thing using CPU to any significant degree. Also CPU Usage History show that the CPU Usage never reaches 100%.
2) I sent a new test program that will log test execution time in more places. Longer execution times are seen in nearly every area of the program, but one area where this is very dramatic is the time taken to return from one particular subsequence call. In this subsequence I log the time just before the <End Group> at then end of Main. There is nothing in Cleanup. I then log the time immediately after returning from this sequence. On the test system I have here this takes approximately 160 ms. On the test system at the factory this takes approximately 14.5 seconds! The program seems to be hanging here for some reason. Every time this function is called the same thing happens and for the same amount of time (and this function is called about 40 times in the test program, so this is kill me).

Execution time of procedures

How can find out the execution time of procedures.
I've debug and find why a procedure takes so much time for its execution.
Could someone please help me with tips or links to useful info.

First you can use the SQLPlus feature "set timing on" This will print the run time of each SQL or pl/sql procedure executed in the session.
Second you can modify the pl/sql code to include timing information so as the code runs it dumps and/or calculates step and procedure run time.
Third look at the dbms_profiler package Oracle provides.
HTH -- Mark D Powell --

Execution Time in minutes

Hi,
it´s me again with another question.
The Execution Time in the test report (xml) is always displayed in seconds. How can I change this in minutes?
Thanks a lot.
Daniel

Thats not so easy to achive, because there is no option for this in the "Configure-->Report Options..." menu.
You could change the "Add Start Time XML" Step in the "AddReportHeader" Sequence in the ...\National Instruments\TestStand 3.1\Components\NI\Models\TestSTandModels\reportgen_xml.seq Sequence-File.
Another way would be to adjust the Stylesheet (...\National Instruments\TestStand 3.1\Components\NI\Models\TestSTandModels\StyleSheets\)
For both you need knowlwedge about XML...

Execution time in minutes and seconds

In the UUT Report, the Execution Time displays in seconds. How can I get that to display in minutes and seconds.

I'm just now getting to this, and I've decided to address this in the reportgen_html.seq. In the step labelled "Add Execution Time", the expression reads,
Locals.Header += "<TR><TD NOWRAP='NOWRAP'><LI>" + ResStr("MODEL", "RPT_HEADER_EXEC_TIME") + "<TD>" + (PropertyExists("Parameters.MainSequenceResults.TS.TotalTime") ? Str(Parameters.MainSequenceResults.TS.TotalTime, Parameters.ReportOptions.NumericFormat , 1, True) + ResStr("MODEL", "RPT_HEADER_SECONDS") : ResStr("MODEL", "RPT_NOT_APPLICABLE")) + "\n"
I found the RPT_HEADER_SECONDS constant and changed it to _MINUTES and changed the string. I divided the Parameters.MainSequenceResults.TS.TotalTime by 60, and this all seems to work. The only thing that's not working is that I'm updating the Parameters.ReportOptions.NumericFormat, and no matter what I do it keeps showing me 13 decimal points.
The Parameters.ReportOptions.NumericFormat is set to %$.13f (but I've tried several variations).
I just want it to display something like 21.63 minutes. Also, what is the $ doing in that expression

Slow query execution time

Hi,
I have a query which fetches around 100 records from a table which has approximately 30 million records. Unfortunately, I have to use the same table and can't go ahead with a new table.
The query executes within a second from RapidSQL. The problem I'm facing is it takes more than 10 minutes when I run it through the Java application. It doesn't throw any exceptions, it executes properly.
The query:
SELECT aaa, bbb, SUM(ccc), SUM(ddd), etc
FROM MyTable
WHERE SomeDate= date_entered_by_user AND SomeString IN ("aaa","bbb")
GROUP BY aaa,bbbI have an existing clustered index on SomeDate and SomeString fields.
To check I replaced the where clause with
WHERE SomeDate= date_entered_by_user AND SomeString = "aaa"No improvements.
What could be the problem?
Thank you,
Lobo

It's hard for me to see how a stored proc will address this problem. I don't think it changes anything. Can you explain? The problem is slow query execution time. One way to speed up the execution time inside the RDBMS is to streamline the internal operations inside the interpreter.
When the engine receives a command to execute a SQL statement, it does a few things before actually executing the statement. These things take time. First, it checks to make sure there are no syntax errors in the SQL statement. Second, it checks to make sure all of the tables, columns and relationships "are in order." Third, it formulates an execution plan. This last step takes the most time out of the three. But, they all take time. The speed of these processes may vary from product to product.
When you create a stored procedure in a RDBMS, the processes above occur when you create the procedure. Most importantly, once an execution plan is created it is stored and reused whenever the stored procedure is ran. So, whenever an application calls the stored procedure, the execution plan has already been created. The engine does not have to anaylze the SELECT|INSERT|UPDATE|DELETE statements and create the plan (over and over again).
The stored execution plan will enable the engine to execute the query faster.
/>

TO REDUCE THE EXECUTION TIME OF REPORT

HI,
 CAN ANYONE TELL ME THAT, HOW CAN I REDUCE THE EXECUTION TIME OF THE REPORT. IS THERE ANY IDEA TO IMPROVE THE PERFORMANCE OF THE REPORT.

Hi Santosh,
Good check out the following documentation
Performance tuning
For all entries
Nested selects
Select using JOINS
Use the selection criteria
Use the aggregated functions
Select with view
Select with index support
Select Into table
Select with selection list
Key access to multiple lines
Copying internal tables
Modifying a set of lines
Deleting a sequence of lines
Linear search vs. binary
Comparison of internal tables
Modify selected components
Appending two internal tables
Deleting a set of lines
Tools available in SAP to pin-point a performance problem
Optimizing the load of the database
For all entries
The for all entries creates a where clause, where all the entries in the driver table are combined with OR. If the number of entries in the driver table is larger than rsdb/max_blocking_factor, several similar SQL statements are executed to limit the length of the WHERE clause.
The plus
Large amount of data
Mixing processing and reading of data
Fast internal reprocessing of data
Fast
The Minus
Difficult to program/understand
Memory could be critical (use FREE or PACKAGE size)
Some steps that might make FOR ALL ENTRIES more efficient:
Removing duplicates from the the driver table
Sorting the driver table
If possible, convert the data in the driver table to ranges so a BETWEEN statement is used instead of and OR statement:
FOR ALL ENTRIES IN i_tab
WHERE mykey >= i_tab-low and
 mykey <= i_tab-high.
Nested selects
The plus:
Small amount of data
Mixing processing and reading of data
Easy to code - and understand
The minus:
Large amount of data
when mixed processing isnt needed
Performance killer no. 1
Select using JOINS
The plus
Very large amount of data
Similar to Nested selects - when the accesses are planned by the programmer
In some cases the fastest
Not so memory critical
The minus
Very difficult to program/understand
Mixing processing and reading of data not possible
Use the selection criteria
SELECT * FROM SBOOK.
CHECK: SBOOK-CARRID = 'LH' AND
 SBOOK-CONNID = '0400'.
ENDSELECT.
SELECT * FROM SBOOK
WHERE CARRID = 'LH' AND
 CONNID = '0400'.
ENDSELECT.
Use the aggregated functions
C4A = '000'.
SELECT * FROM T100
WHERE SPRSL = 'D' AND
 ARBGB = '00'.
CHECK: T100-MSGNR > C4A.
C4A = T100-MSGNR.
ENDSELECT.
SELECT MAX( MSGNR ) FROM T100 INTO C4A
WHERE SPRSL = 'D' AND
 ARBGB = '00'.
Select with view
SELECT * FROM DD01L
WHERE DOMNAME LIKE 'CHAR%'
 AND AS4LOCAL = 'A'.
SELECT SINGLE * FROM DD01T
 WHERE DOMNAME = DD01L-DOMNAME
 AND AS4LOCAL = 'A'
 AND AS4VERS = DD01L-AS4VERS
 AND DDLANGUAGE = SY-LANGU.
ENDSELECT.
SELECT * FROM DD01V
WHERE DOMNAME LIKE 'CHAR%'
 AND DDLANGUAGE = SY-LANGU.
ENDSELECT.
Select with index support
SELECT * FROM T100
WHERE ARBGB = '00'
 AND MSGNR = '999'.
ENDSELECT.
SELECT * FROM T002.
SELECT * FROM T100
 WHERE SPRSL = T002-SPRAS
 AND ARBGB = '00'
 AND MSGNR = '999'.
ENDSELECT.
ENDSELECT.
Select Into table
REFRESH X006.
SELECT * FROM T006 INTO X006.
APPEND X006.
ENDSELECT
SELECT * FROM T006 INTO TABLE X006.
Select with selection list
SELECT * FROM DD01L
WHERE DOMNAME LIKE 'CHAR%'
 AND AS4LOCAL = 'A'.
ENDSELECT
SELECT DOMNAME FROM DD01L
INTO DD01L-DOMNAME
WHERE DOMNAME LIKE 'CHAR%'
 AND AS4LOCAL = 'A'.
ENDSELECT
Key access to multiple lines
LOOP AT TAB.
CHECK TAB-K = KVAL.
ENDLOOP.
LOOP AT TAB WHERE K = KVAL.
ENDLOOP.
Copying internal tables
REFRESH TAB_DEST.
LOOP AT TAB_SRC INTO TAB_DEST.
APPEND TAB_DEST.
ENDLOOP.
TAB_DEST[] = TAB_SRC[].
Modifying a set of lines
LOOP AT TAB.
IF TAB-FLAG IS INITIAL.
 TAB-FLAG = 'X'.
ENDIF.
MODIFY TAB.
ENDLOOP.
TAB-FLAG = 'X'.
MODIFY TAB TRANSPORTING FLAG
 WHERE FLAG IS INITIAL.
Deleting a sequence of lines
DO 101 TIMES.
DELETE TAB_DEST INDEX 450.
ENDDO.
DELETE TAB_DEST FROM 450 TO 550.
Linear search vs. binary
READ TABLE TAB WITH KEY K = 'X'.
READ TABLE TAB WITH KEY K = 'X' BINARY SEARCH.
Comparison of internal tables
DESCRIBE TABLE: TAB1 LINES L1,
 TAB2 LINES L2.
IF L1 <> L2.
TAB_DIFFERENT = 'X'.
ELSE.
TAB_DIFFERENT = SPACE.
LOOP AT TAB1.
 READ TABLE TAB2 INDEX SY-TABIX.
 IF TAB1 <> TAB2.
 TAB_DIFFERENT = 'X'. EXIT.
 ENDIF.
ENDLOOP.
ENDIF.
IF TAB_DIFFERENT = SPACE.
ENDIF.
IF TAB1[] = TAB2[].
ENDIF.
Modify selected components
LOOP AT TAB.
TAB-DATE = SY-DATUM.
MODIFY TAB.
ENDLOOP.
WA-DATE = SY-DATUM.
LOOP AT TAB.
MODIFY TAB FROM WA TRANSPORTING DATE.
ENDLOOP.
Appending two internal tables
LOOP AT TAB_SRC.
APPEND TAB_SRC TO TAB_DEST.
ENDLOOP
APPEND LINES OF TAB_SRC TO TAB_DEST.
Deleting a set of lines
LOOP AT TAB_DEST WHERE K = KVAL.
DELETE TAB_DEST.
ENDLOOP
DELETE TAB_DEST WHERE K = KVAL.
Tools available in SAP to pin-point a performance problem
The runtime analysis (SE30)
SQL Trace (ST05)
Tips and Tricks tool
The performance database
Optimizing the load of the database
Using table buffering
Using buffered tables improves the performance considerably. Note that in some cases a stament can not be used with a buffered table, so when using these staments the buffer will be bypassed. These staments are:
Select DISTINCT
ORDER BY / GROUP BY / HAVING clause
Any WHERE clasuse that contains a subquery or IS NULL expression
JOIN s
A SELECT... FOR UPDATE
If you wnat to explicitly bypass the bufer, use the BYPASS BUFFER addition to the SELECR clause.
Use the ABAP SORT Clause Instead of ORDER BY
The ORDER BY clause is executed on the database server while the ABAP SORT statement is executed on the application server. The datbase server will usually be the bottleneck, so sometimes it is better to move thje sort from the datsbase server to the application server.
If you are not sorting by the primary key ( E.g. using the ORDER BY PRIMARY key statement) but are sorting by another key, it could be better to use the ABAP SORT stament to sort the data in an internal table. Note however that for very large result sets it might not be a feasible solution and you would want to let the datbase server sort it.
Avoid ther SELECT DISTINCT Statement
As with the ORDER BY clause it could be better to avoid using SELECT DISTINCT, if some of the fields are not part of an index. Instead use ABAP SORT + DELETE ADJACENT DUPLICATES on an internal table, to delete duplciate rows.
Good Luck and thanks
AK

Alert with event for delayed job and long execution time

Dear All,
We are planning to send alert via email in case job delayed or long execution time.
I have followed below steps:
1) Create event Raise Event when job is delayed.
2) create job chain with STEP1, Job 1 and assign event in raise event parameter.
3) Once job chain delayed it should raise events.
4) Above event should trigger custom email but I can not put the Mail_To parameter as IN parameter. And can not be recognized during
execution.
It ends with the below error.
Details:
JCS-122035: Unable to persist: JCS-102075: Mandatory parameter not set: Parameter Mail_To for job 20413
at com.redwood.scheduler.model.SchedulerSessionImpl.writeDirtyListLocal(SchedulerSessionImpl.java:805)
at com.redwood.scheduler.model.SchedulerSessionImpl.persist(SchedulerSessionImpl.java:757)
Please let us know if anybody knows how to add Mail_To parameter to script.
Any help is appreciated.
Thanks in advance.
Regards,
Jiggi

Dear Jiggi,
where will you define execution time of particular job? because some jobs will take only 1 or 2 minutes, but some jobs normally take more than hours, so how will you decide execution time of individual jobs?
i thinks you can use P_TO Parameter for sending mail, if you want to add some output log activate spool output script.
Thanks and regards
Muhammad Asif

Last one month jobs execution time in sql server 2008 r2

Dear Friends,
We configured replication between three servers two are publishers and one subscriber for two publisher.
my question is daily basis one job running on subscriber end it truncate and insert the data every night .
unfortunately today job was failed I observed in jobs view history. but client requirement manually run the job and data dump into the table. but I want know its previous execution time as per that I will run the job in production hours but in jobs view
history showing only today's fail job history. how to find the last execution time .
note: yesterday job was successfully completed.
Message
Executed as user: NT AUTHORITY\SYSTEM. Cannot initialize the data source object of OLE DB provider "SQLNCLI10" for linked server "server name". [SQLSTATE 42000] (Error 7303) OLE DB provider "SQLNCLI10" for linked
server "server name" returned message "Unable to complete login process due to delay in opening server connection". [SQLSTATE 01000] (Error 7412). The step failed.
mastanvali shaik

But what about to that particular job ? what is the name of the job ? Please assign that job name in the below script and check .. Its sure that history is not exist for that particular job anyway for your confirmation please use the below scripts and try...
make sure to add the name .. when was the last backup taken for your system databases ?
WHERE JOB.name = 'Your JobName' -- Add your job name..
SELECT [JobName] = JOB.name,
[Step] = HIST.step_id,
[StepName] = HIST.step_name,
[Message] = HIST.message,
[Status] = CASE WHEN HIST.run_status = 0 THEN 'Failed'
WHEN HIST.run_status = 1 THEN 'Succeeded'
WHEN HIST.run_status = 2 THEN 'Retry'
WHEN HIST.run_status = 3 THEN 'Canceled'
END,
[RunDate] = HIST.run_date,
[RunTime] = HIST.run_time,
[Duration] = HIST.run_duration
FROM sysjobs JOB
INNER JOIN sysjobhistory HIST ON HIST.job_id = JOB.job_id
WHERE JOB.name = 'Your JobName'
ORDER BY HIST.run_date, HIST.run_time
Raju Rasagounder Sr MSSQL DBA

SAP BO Report Execution time and Record count

Hi All,
We have a requirement to set the limits on report execution time and record count centrally. Can you please help me to identify where exactly we have to define the settings in CMC for BO4.
Thanks in advance,
Shalini

Hi Shalini,
Please follow these steps, also check in for any more details if any;
Step 1: Launch CMC
Step 2: Select Servers
Step 3: Select Web Intelligence processing Server, right click and Goto Properties
Step 4: Maximum List Of Values Size (entries) default value is 50000.
Step 5: Increase this value if your "LOVS" greater than this value.
Step 6: Save and close.
Step 7: Restart the server.
Hope this helps.
- Ram

Portal report execution time

Hi experts,
Can any one tell me how to check the report execution time in portal.Its taking a long time to execute
the report in portal.so i would like to evaluate the execution time in portal itself.
I know how to check it at bi side but here iam intrested to know at portal itself and it varies
at bi side RSRT and at portal level. At RSRT and in Analyzer its taking expected time only but in
portal its taking long time.
Regards,
Shais

Thanks Alot For your reply.
Its working. when i run the statistics i got the below details .
Step runtime: 7532 ms -
> is this the total time taken to execute the report?
Remote runtime :6845 ms
Local runtime :687 ms
Handle types olap frontend events:
- BRFC: 78 ms
- DP: 237 ms
- OLAP: 6443 ms
- DFLT: 95 ms
- DIAL: 0 ms
- APPL: 391 ms
- F4: 4 ms
- CMD: 110 ms
- ITEM: 109 ms
what is meant by remote run time, local run time,BRFC .......... Can you explain me in details.
Waiting for your reply,
Regards,
Shais.

Execution time of IVI Steps

Similar Messages

Maybe you are looking for