Profile Performance and Memory - VI Time Analysis

[Raul2203]

Hi all,

I did a performance check on my measurement application using Profile Performance and Memory Tool.

The performance report is as shown below.

As it can be seen in the above figure, the time required for my main vi i.e RT.Main.ATLAS is shown 61.128 secs.

Could anyone please explain me how I am getting such big values for VI times?

I expect the VI times to be in few milliseconds and want them to be as less as possible.

Thanks in advance!

Rahul

[GerdW]

Hi Raul,

As it can be seen in the above figure,

Nope, can't be seen…

- using the profiling tool will influence the VI timings…

- you should attach your VI when you want us to suggest improvements…

[nathand]

---

@Raul2203 wrote:

As it can be seen in the above figure, the time required for my main vi i.e RT.Main.ATLAS is shown 61.128 secs.

Could anyone please explain me how I am getting such big values for VI times?

I expect the VI times to be in few milliseconds and want them to be as less as possible.

---

That's the total amount of time the VI spent running, over all the loop iterations. For the main VI, the VI may not be doing anything, but it's still running. You'll note that your image shows only 1 run of RT.Main.ATLAS, which is exactly what you'd expect. It's the main VI and runs continuously. The running time for your Main VI should be the amount of time since you started running it - did you take this snapshot about a minute after you started the VI?

If you want to know how long it takes a VI to execute once, look at the Average (as well as Shortest and Longest) column.

---

@GerdW wrote:

As it can be seen in the above figure,

Nope, can't be seen…

---

Following the trick mentioned here: http://forums.ni.com/t5/BreakPoint/Rube-Goldberg-Code/m-p/3282518#M28095 you can see the full-size image.