Analyzers
Talk to fellow users of Intel Analyzer tools (Intel VTune™ Profiler, Intel Advisor)
Announcements
FPGA community forums and blogs on community.intel.com are migrating to the new Altera Community and are read-only. For urgent support needs during this transition, please visit the FPGA Design Resources page or contact an Altera Authorized Distributor.
5255 Discussions

How to set the application running times in vtune?

newlife2003
Beginner
‎09-29-2003 02:45 AM
770 Views
Hi, all.
Generally, when the vtune sampls an application, the application runs for 2 times for an approximatly precise result. But if I want the application to run for just one time, how should I do? thanks
0 Kudos

Link Copied

1 Reply
jeffrey-gallagher
Beginner
‎09-29-2003 03:21 PM
770 Views
Hey newlife2003

That first run is called a calibration run, and it's currently vtl's default behavior to include it. To stop it from happening, add -o "-cal no" to your command line, for example:

vtl activity -c sampling -o "-cal no" -app /bin/ls run


By default, vtl currently runs a calibration session (default, 20 seconds) before running your application for the session you've asked for.

You can stop this by turning calibration off at the command line by adding -o "-cal no" as I mentioned above(do a man page on sampling for more info).

$ man sampling

Please note that the engineering team is considering currently turning calibration OFF by default by the time the new 2.0 beta software is released.

0 Kudos
Copy link
Reply

Community support is provided Monday to Friday. Other contact methods are available here.

Intel does not verify all solutions, including but not limited to any file transfers that may appear in this community. Accordingly, Intel disclaims all express and implied warranties, including without limitation, the implied warranties of merchantability, fitness for a particular purpose, and non-infringement, as well as any warranty arising from course of performance, course of dealing, or usage in trade.

For more complete information about compiler optimizations, see our Optimization Notice.