report-knob

例

この例は、HPC パフォーマンス特性解析結果のサマリーレポートを生成して、問題の説明をスキップします。

    vtune -report summary -r r001hpc -report-knob show-issues=false
    vtune: Executing actions 75 % Generating a report
    Elapsed Time: 23.182s
    GFLOPS: 14.748
    CPU Utilization: 58.0%
        Average CPU Usage: 13.920 Out of 24 logical CPUs
        Serial Time: 0.069s (0.3%)
        Parallel Region Time: 23.113s (99.7%)
            Estimated Ideal Time: 14.010s (60.4%)
            OpenMP Potential Gain: 9.103s (39.3%)
    Memory Bound: 0.446
        Cache Bound: 0.175
        DRAM Bound: 0.216
        NUMA: % of Remote Accesses: 38.3%
    FPU Utilization: 2.7%
        GFLOPS: 14.748
            Scalar GFLOPS: 4.801
            Packed GFLOPS: 9.947
    Collection and Platform Info
        Application Command Line: ./sp.B.x
        User Name: vtune
        Operating System: 3.10.0-327.el7.x86_64 NAME="Red Hat Enterprise Linux Server" VERSION="7.2 (Maipo)" ID="rhel" ID_LIKE="fedora" VERSION_ID="7.2" P
    RETTY_NAME="Red Hat Enterprise Linux Server 7.2 (Maipo)" ANSI_COLOR="0;31" CPE_NAME="cpe:/o:redhat:enterprise_linux:7.2:GA:server" HOME_URL="https://w
    ww.redhat.com/" BUG_REPORT_URL="https://bugzilla.redhat.com/"  REDHAT_BUGZILLA_PRODUCT="Red Hat Enterprise Linux 7" REDHAT_BUGZILLA_PRODUCT_VERSION=7.
    2 REDHAT_SUPPORT_PRODUCT="Red Hat Enterprise Linux" REDHAT_SUPPORT_PRODUCT_VERSION="7.2"
        Computer Name: test
        Result Size: 1 GB
        Collection start time: 19:04:30 13/07/2016 UTC
        Collection stop time: 19:04:53 13/07/2016 UTC
        Name: Intel® Xeon® E5/E7 v2 Processor code named Ivytown
        Frequency: 2.694 GHz
        Logical CPU Count: 24
        CPU
            Name: Intel® Xeon® E5/E7 v2 Processor code named Ivytown
            Frequency: 2.694 GHz
            Logical CPU Count: 24

この例は、HPC パフォーマンス特性解析の結果サマリーレポートを生成して、問題の説明をスキップします。

    vtune -report summary -r r001hpc -report-knob show-issues=true
    vtune: Executing actions 75 % Generating a report
    Elapsed Time: 23.182s
    GFLOPS: 14.748
    CPU Utilization: 58.0%
     | The metric value is low, which may signal a poor logical CPU cores
     | utilization caused by load imbalance, threading runtime overhead, contended
     | synchronization, or thread/process underutilization. Explore CPU Utilization
     | sub-metrics to estimate the efficiency of MPI and OpenMP parallelism or run
     | the Threading analysis to identify parallel bottlenecks for other
     | parallel runtimes.
     |
        Average CPU Usage: 13.920 Out of 24 logical CPUs
        Serial Time: 0.069s (0.3%)
        Parallel Region Time: 23.113s (99.7%)
            Estimated Ideal Time: 14.010s (60.4%)
            OpenMP Potential Gain: 9.103s (39.3%)
             | The time wasted on load imbalance or parallel work arrangement is
             | significant and negatively impacts the application performance and
             | scalability. Explore OpenMP regions with the highest metric values.
             | Make sure the workload of the regions is enough and the loop schedule
             | is optimal.
             |
    ...