# N/A instructions executed

**URL:** <https://forums.developer.nvidia.com/t/n-a-instructions-executed/154342>\
**Category:** Nsight Compute\
**Created:** [September 14, 2020, 4:41pm UTC](https://forums.developer.nvidia.com/t/n-a-instructions-executed/154342 "2020-09-14T16:41:54Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![mahmood.nt](https://developer.download.nvidia.com/images/forums/profile-default-devtalk-84.png) [@mahmood.nt](https://forums.developer.nvidia.com/u/mahmood.nt)\
**Post date:** [September 14, 2020, 4:41pm UTC](https://forums.developer.nvidia.com/t/n-a-instructions-executed/154342/1 "2020-09-14T16:41:54Z")

</div>

Hi  
As you can see in the report below, the metric related to executed instructions is n/a while some other metrics, such as dram and sm efficiency are non-zero. What does that mean? Is something wrong here?

```
    ---------------------------------------------------------------------- --------------- ------------------------------
    dram__sectors_read.sum sector 94,079
    dram__sectors_write.sum sector 32,101
    sm__cycles_active.avg.pct_of_peak_sustained_elapsed % 92.69
    smsp__inst_executed (!) n/a
    smsp__thread_inst_executed (!) n/a
    ---------------------------------------------------------------------- --------------- ------------------------------

```

I am using the latest version.

```
$ nv-nsight-cu-cli --version
NVIDIA (R) Nsight Compute Command Line Profiler
Copyright (c) 2012-2019 NVIDIA Corporation
Version 2019.5.0 (Build 27346997)

```

---

<div class="post-metadata">

**Author:** ![Greg](https://sea2.discourse-cdn.com/nvidia/user_avatar/forums.developer.nvidia.com/greg/32/14043_2.png) [@Greg](https://forums.developer.nvidia.com/u/Greg)\
**Post date:** [September 17, 2020, 5:51am UTC](https://forums.developer.nvidia.com/t/n-a-instructions-executed/154342/2 "2020-09-17T05:51:29Z")

</div>

n/a appears if the metric cannot be collected. In this case I believe you are manually specifying the metric and you have not provided the sub-metric which can be

Counters : may be either a raw counter from the GPU, or a calculated counter value. Every counter has 4 sub-metrics under it:

| .sum | The sum of counter values across all unit instances. |
| --- | --- |
| .avg | The average counter value across all unit instances. |
| .min | The minimum counter value across all unit instances. |
| .max | The maximum counter value across all unit instances. |

For more information see the Nsight Compute Profiling Guide section [3.2 Metrics Structure](https://docs.nvidia.com/nsight-compute/ProfilingGuide/index.html#metrics-structure).