LabVIEW
Number of cycles?
@Zourvan wrote:exactly I try to find both of them VI execution time and wire so trigger VI 2, indeed the wire should have time to trigger VI 2!
Sorry, I don't understand what you mean here. Did you look at my linked presentation and examples?
As I said, the wire just defines a data dependency, meaning VI2 cannot start until VI1 has completed. It is up to the compiler and scheduler to decide what happens after VI1 has executed and before VI2 starts, depending on what other parallel parts of your code also want to run. If your CPU has multiple cores, several things can even happen at the same time if they don't depend on each other.
Again, what are your performance requirements and concerns. Do you want to define an exact time between the two subVIs or do you just want to measure the elapsed time? Is it currently too slow? All moderns CPUs have multiple cores, several cache levels, (hyperthreading), and other advanced internal architectures that make it impossible to boil some random code down to an exact number of clock cycles. Also, don't forget that your PC also runs several hundred of other processes at the same time. Once you go to a Realtime OS, things become a bit more deterministic.
This is using the Flat Sequence Structure and the High Resolution Relative Seconds.vi
@Zourvan wrote:
Dear pallen
Thank you for your answer.
but it's so bad, In visual Studio, and Intel Parallel Studio it done easy way.
I have no idea what this studio is, but maybe you're looking for the VI profiler under Tools -> Profile -> Performance and Memory. Though that was not what you asked for in your original post.
/Y
