LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Performance Profiler with Sub-Panel linked VI's

I've got a Main vi which contains a tab control, each page holding a subpanel linked to a SubVI. When using the Performance and Memory Profiler my Main.vi is the only one that shows up, so the timing information isn't very useful. If I get a Snapshot while the profiler is running it shows the linked subVI's as being in memory, but doesn't show any timing information on them (All 0.0's for all vi's including Main).

 

Am I doing something incorrectly?

Download All
0 Kudos
Message 1 of 6
(2,977 Views)

Sorry for the bump, but...

Any ideas on this? If what I'm trying to do isn't possible I'll live, but timing info on my subpanel-linked VI's would definitely be nice to have.

0 Kudos
Message 2 of 6
(2,949 Views)
Hmm.. I haven't come across this before, but I suspect it may not be possible (with this particular tool).  However, I would like to play with things a bit before I say for sure. 
Brian A.
National Instruments
Applications Engineer
Message 3 of 6
(2,925 Views)

Looks like you are doing everything correctly.  The problem is somewhere between how the SubPanel deals with VIs in memory, and where the Profiler gets its data.  You should be able to see stats for your main VI once you stop it, but not the subVIs you are loading into the panel.  Sorry if this isn't what you were looking for, but at least we can say that it is not you doing anything wrong.  I would head on over to the Product Suggestion Center and submit this (these are taken seriously!).  It's certainly a valid use case that may not have been considered yet.

 

Cheers, 

Brian A.
National Instruments
Applications Engineer
0 Kudos
Message 4 of 6
(2,911 Views)
I do this exact thing in my main project. I'm handling my subpanel VIs  through static references, which loads them into memory. I suspect your using the open vi reference primitive, which doesn't. I'm guessing the problem is that you need to have the VIs loaded into memory before you run the profiler (which annoying crashes alot on me when I try to profile my main project). You could try putting down some static references. Or open a seperate vi and put the subpanel vis as subvis in it. You're not going to run it. it's just there to keep the subpanel vis in loaded in memory.
Message 5 of 6
(2,898 Views)
Nice work-around ideas.  Thanks Matt.
Brian A.
National Instruments
Applications Engineer
0 Kudos
Message 6 of 6
(2,888 Views)