Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Highlighted
Beginner
20 Views

Is a bug? Run astar benchmark many times execute once.

HI,

I have run astar to output but I found it runs many times of the benchmark, it seems still continue, I attached it, but this runs well in my previous computer.

Is this a bug?

 

 

 

 

 

runspec v4662 - Copyright 1999-2006 Standard Performance Evaluation Corporation
Using 'unknown' tools
Reading MANIFEST... 17857 files
Loading runspec modules...............
Locating benchmarks...found 31 benchmarks in 12 benchsets.
Locating output formats: ASCII, config, CSV, flags, HTML, mail, PDF, PostScript, raw, Screen, Submission Check
Reading config file '/home/foo/SPEC/foo/SPEC/cpu2006/config/myicc2.cfg'
Benchmarks selected: 473.astar
Compiling Binaries
  Up to date 473.astar ref base cpu2006.linux64 default


Parsing Flags
  Looking at 473.astar base cpu2006.linux64 default: done
Flag Parsing Complete

Setting Up Run Directories
  Setting up 473.astar ref base cpu2006.linux64 default: 
Notice: Unusable path detected in run directory list file.
  /home/foo/SPEC/foo/SPEC/cpu2006/benchspec/CPU2006/473.astar/run/list
references one or more paths which will be ignored, because they are
not subdirectories of this run directory.  This condition may be a
result of having moved your SPEC benchmark tree.  If that's what happened,
and if you don't need the old run directories, you can just remove
them, along with the list file.  (Usually it's safe to delete old
run directories, as they are automatically re-created when needed.)


existing (run_base_ref_cpu2006.linux64.0003)
Running Benchmarks
  Running 473.astar ref base cpu2006.linux64 default
Success: 1x473.astar
Producing Reports
mach: default
  ext: cpu2006.linux64
    size: ref
      set: int
        format: raw -> /home/foo/SPEC/foo/SPEC/cpu2006/result/CINT2006.12668.rsf
        format: flags -> /home/foo/SPEC/foo/SPEC/cpu2006/result/CINT2006.12668.flags.html
        format: ASCII -> /home/foo/SPEC/foo/SPEC/cpu2006/result/CINT2006.12668.txt
        format: HTML -> /home/foo/SPEC/foo/SPEC/cpu2006/result/CINT2006.12668.html, CINT2006.12668.gif
      set: fp

The log for this run is in /home/foo/SPEC/foo/SPEC/cpu2006/result/CPU2006.12668.log

runspec finished at Tue Sep 13 16:29:57 2016; 216 total seconds elapsed
Warning: Attribute 'anythr' is not allowed. Discarded
runspec v4662 - Copyright 1999-2006 Standard Performance Evaluation Corporation
Using 'unknown' tools
Reading MANIFEST... 17857 files
Loading runspec modules...............
Locating benchmarks...found 31 benchmarks in 12 benchsets.
Locating output formats: ASCII, config, CSV, flags, HTML, mail, PDF, PostScript, raw, Screen, Submission Check
Reading config file '/home/foo/SPEC/foo/SPEC/cpu2006/config/myicc2.cfg'
Benchmarks selected: 473.astar
Compiling Binaries
  Up to date 473.astar ref base cpu2006.linux64 default


Parsing Flags
  Looking at 473.astar base cpu2006.linux64 default: done
Flag Parsing Complete

Setting Up Run Directories
  Setting up 473.astar ref base cpu2006.linux64 default: 
Notice: Unusable path detected in run directory list file.
  /home/foo/SPEC/foo/SPEC/cpu2006/benchspec/CPU2006/473.astar/run/list
references one or more paths which will be ignored, because they are
not subdirectories of this run directory.  This condition may be a
result of having moved your SPEC benchmark tree.  If that's what happened,
and if you don't need the old run directories, you can just remove
them, along with the list file.  (Usually it's safe to delete old
run directories, as they are automatically re-created when needed.)


existing (run_base_ref_cpu2006.linux64.0003)
Running Benchmarks
  Running 473.astar ref base cpu2006.linux64 default
Success: 1x473.astar
Producing Reports
mach: default
  ext: cpu2006.linux64
    size: ref
      set: int
        format: raw -> /home/foo/SPEC/foo/SPEC/cpu2006/result/CINT2006.12669.rsf
        format: flags -> /home/foo/SPEC/foo/SPEC/cpu2006/result/CINT2006.12669.flags.html
        format: ASCII -> /home/foo/SPEC/foo/SPEC/cpu2006/result/CINT2006.12669.txt
        format: HTML -> /home/foo/SPEC/foo/SPEC/cpu2006/result/CINT2006.12669.html, CINT2006.12669.gif
      set: fp

The log for this run is in /home/foo/SPEC/foo/SPEC/cpu2006/result/CPU2006.12669.log

runspec finished at Tue Sep 13 16:33:42 2016; 223 total seconds elapsed
Warning: Attribute 'anythr' is not allowed. Discarded
runspec v4662 - Copyright 1999-2006 Standard Performance Evaluation Corporation
Using 'unknown' tools
Reading MANIFEST... 17857 files
Loading runspec modules...............
Locating benchmarks...found 31 benchmarks in 12 benchsets.
Locating output formats: ASCII, config, CSV, flags, HTML, mail, PDF, PostScript, raw, Screen, Submission Check
Reading config file '/home/foo/SPEC/foo/SPEC/cpu2006/config/myicc2.cfg'
Benchmarks selected: 473.astar
Compiling Binaries
  Up to date 473.astar ref base cpu2006.linux64 default


Parsing Flags
  Looking at 473.astar base cpu2006.linux64 default: done
Flag Parsing Complete

Setting Up Run Directories
  Setting up 473.astar ref base cpu2006.linux64 default: 
Notice: Unusable path detected in run directory list file.
  /home/foo/SPEC/foo/SPEC/cpu2006/benchspec/CPU2006/473.astar/run/list
references one or more paths which will be ignored, because they are
not subdirectories of this run directory.  This condition may be a
result of having moved your SPEC benchmark tree.  If that's what happened,
and if you don't need the old run directories, you can just remove
them, along with the list file.  (Usually it's safe to delete old
run directories, as they are automatically re-created when needed.)


existing (run_base_ref_cpu2006.linux64.0003)
Running Benchmarks
  Running 473.astar ref base cpu2006.linux64 default
Success: 1x473.astar
Producing Reports
mach: default
  ext: cpu2006.linux64
    size: ref
      set: int
        format: raw -> /home/foo/SPEC/foo/SPEC/cpu2006/result/CINT2006.12670.rsf
        format: flags -> /home/foo/SPEC/foo/SPEC/cpu2006/result/CINT2006.12670.flags.html
        format: ASCII -> /home/foo/SPEC/foo/SPEC/cpu2006/result/CINT2006.12670.txt
        format: HTML -> /home/foo/SPEC/foo/SPEC/cpu2006/result/CINT2006.12670.html, CINT2006.12670.gif
      set: fp

The log for this run is in /home/foo/SPEC/foo/SPEC/cpu2006/result/CPU2006.12670.log

runspec finished at Tue Sep 13 16:37:18 2016; 214 total seconds elapsed
Warning: Attribute 'anythr' is not allowed. Discarded
runspec v4662 - Copyright 1999-2006 Standard Performance Evaluation Corporation
Using 'unknown' tools
Reading MANIFEST... 17857 files
Loading runspec modules...............
Locating benchmarks...found 31 benchmarks in 12 benchsets.
Locating output formats: ASCII, config, CSV, flags, HTML, mail, PDF, PostScript, raw, Screen, Submission Check
Reading config file '/home/foo/SPEC/foo/SPEC/cpu2006/config/myicc2.cfg'
Benchmarks selected: 473.astar
Compiling Binaries
  Up to date 473.astar ref base cpu2006.linux64 default


Parsing Flags
  Looking at 473.astar base cpu2006.linux64 default: done
Flag Parsing Complete

Setting Up Run Directories
  Setting up 473.astar ref base cpu2006.linux64 default: 
Notice: Unusable path detected in run directory list file.
  /home/foo/SPEC/foo/SPEC/cpu2006/benchspec/CPU2006/473.astar/run/list
references one or more paths which will be ignored, because they are
not subdirectories of this run directory.  This condition may be a
result of having moved your SPEC benchmark tree.  If that's what happened,
and if you don't need the old run directories, you can just remove
them, along with the list file.  (Usually it's safe to delete old
run directories, as they are automatically re-created when needed.)


existing (run_base_ref_cpu2006.linux64.0003)
Running Benchmarks
  Running 473.astar ref base cpu2006.linux64 default

 

 

0 Kudos
3 Replies
Highlighted
20 Views

Hello,

According to your prevoius question in this forum you use -allow-multiple-runs option. In combination with event-based sampling analysis it configures VTune to perform as many runs as needed to collect all the PMU events specified in your analysis instead of  collecting them in a single run in event multiplexing mode.

>amplxe-cl.exe -help allow-multiple-runs

Intel(R) VTune(TM) Amplifier Command Line Tool
Copyright (C) 2009-2016 Intel Corporation. All rights reserved.

-allow-multiple-runs | -no-allow-multiple-runs (default)
                              Enable multiple runs to achieve more precise
                              results for hardware event-based collections.
                              When disabled, the collector multiplexes events
                              running a single collection, which lowers result
                              precision.

More details: https://software.intel.com/en-us/node/609434

Regards, Katya

0 Kudos
Highlighted
Beginner
20 Views

ekaterina-logovskaya (Intel) wrote:

Hello,

According to your prevoius question in this forum you use -allow-multiple-runs option. In combination with event-based sampling analysis it configures VTune to perform as many runs as needed to collect all the PMU events specified in your analysis instead of  collecting them in a single run in event multiplexing mode.

>amplxe-cl.exe -help allow-multiple-runs

Intel(R) VTune(TM) Amplifier Command Line Tool
Copyright (C) 2009-2016 Intel Corporation. All rights reserved.

-allow-multiple-runs | -no-allow-multiple-runs (default)
                              Enable multiple runs to achieve more precise
                              results for hardware event-based collections.
                              When disabled, the collector multiplexes events
                              running a single collection, which lowers result
                              precision.

More details: https://software.intel.com/en-us/node/609434

Regards, Katya

 

Hi Katya,

So does this can be executed long time? or does it have the possibility to stop or exit if it runs long time, cause I found in my computer it runs many times or long time and then stop and nothing return, no csv generated.

Thank you.

Have a nice day.

 

0 Kudos
Highlighted
20 Views

Hello,

For multiple-runs mode - collection time and number of runs depends on duration of target application and how many events you have specified in your custom-analysis-*.cfg.

The multiple-runs option is usually recommended for short workloads (<1-2 secs) when event-multiplexing mode doesn't allow to collect meaningfull metrics.

Your bemchmark runs long enough - >210 total seconds elapsed - so try to collect w/o the option and see if a result is generated in a single run.

If you want to stop amplxe-cl collection which was started via script - invoke `amplxe-cl -stop -r <result dir of running collection>` from another console. 

Please also check if you have data-limit option set ? Then collection maybe stopped due to it.

If above doesn't help to get amplxe-cl result - please specify content of your custom-analysis-*.cfg and exact command line.

Regards, Katya

0 Kudos