diff --git a/ADL/metrics/alderlake_metrics_goldencove_core.json b/ADL/metrics/alderlake_metrics_goldencove_core.json index 85dd2b00..35c04f61 100644 --- a/ADL/metrics/alderlake_metrics_goldencove_core.json +++ b/ADL/metrics/alderlake_metrics_goldencove_core.json @@ -6853,7 +6853,7 @@ "MetricName": "Retiring", "LegacyName": "metric_TMA_Retiring(%)", "Level": 1, - "BriefDescription": "This category represents fraction of slots utilized by useful work i.e. issued uops that eventually get retired. Ideally; all pipeline slots would be attributed to the Retiring category. Retiring of 100% would indicate the maximum Pipeline_Width throughput was achieved. Maximizing Retiring typically increases the Instructions-per-cycle (see tma_info_thread_ipc metric). Note that a high Retiring value does not necessary mean there is no room for more performance. For example; Heavy-operations or Microcode Assists are categorized under Retiring. They often indicate suboptimal performance and can often be optimized or avoided. ", + "BriefDescription": "This category represents fraction of slots utilized by useful work i.e. issued uops that eventually get retired. Ideally; all pipeline slots would be attributed to the Retiring category. Retiring of 100% would indicate the maximum Pipeline_Width throughput was achieved. Maximizing Retiring typically increases the Instructions-per-cycle (see IPC metric). Note that a high Retiring value does not necessary mean there is no room for more performance. For example; Heavy-operations or Microcode Assists are categorized under Retiring. They often indicate suboptimal performance and can often be optimized or avoided. ", "UnitOfMeasure": "percent", "Events": [ { diff --git a/ADL/metrics/perf/alderlake_metrics_goldencove_core_perf.json b/ADL/metrics/perf/alderlake_metrics_goldencove_core_perf.json index 99214281..5509d983 100644 --- a/ADL/metrics/perf/alderlake_metrics_goldencove_core_perf.json +++ b/ADL/metrics/perf/alderlake_metrics_goldencove_core_perf.json @@ -872,7 +872,7 @@ "MetricName": "tma_retiring", "ScaleUnit": "100%", "MetricThreshold": "tma_retiring > 0.7 | tma_heavy_operations > 0.1", - "PublicDescription": "This category represents fraction of slots utilized by useful work i.e. issued uops that eventually get retired. Ideally; all pipeline slots would be attributed to the Retiring category. Retiring of 100% would indicate the maximum Pipeline_Width throughput was achieved. Maximizing Retiring typically increases the Instructions-per-cycle (see tma_info_thread_ipc metric). Note that a high Retiring value does not necessary mean there is no room for more performance. For example; Heavy-operations or Microcode Assists are categorized under Retiring. They often indicate suboptimal performance and can often be optimized or avoided. Sample with: UOPS_RETIRED.SLOTS.", + "PublicDescription": "This category represents fraction of slots utilized by useful work i.e. issued uops that eventually get retired. Ideally; all pipeline slots would be attributed to the Retiring category. Retiring of 100% would indicate the maximum Pipeline_Width throughput was achieved. Maximizing Retiring typically increases the Instructions-per-cycle (see IPC metric). Note that a high Retiring value does not necessary mean there is no room for more performance. For example; Heavy-operations or Microcode Assists are categorized under Retiring. They often indicate suboptimal performance and can often be optimized or avoided. Sample with: UOPS_RETIRED.SLOTS.", "DefaultMetricgroupName": "TopdownL1", "MetricGroupnoGroup": "TopdownL1;Default" }, diff --git a/ARL/metrics/arrowlake_metrics_lioncove_core.json b/ARL/metrics/arrowlake_metrics_lioncove_core.json index fbbf8557..c28d971f 100644 --- a/ARL/metrics/arrowlake_metrics_lioncove_core.json +++ b/ARL/metrics/arrowlake_metrics_lioncove_core.json @@ -5561,7 +5561,7 @@ "MetricName": "Retiring", "LegacyName": "metric_TMA_Retiring(%)", "Level": 1, - "BriefDescription": "This category represents fraction of slots utilized by useful work i.e. issued uops that eventually get retired. Ideally; all pipeline slots would be attributed to the Retiring category. Retiring of 100% would indicate the maximum Pipeline_Width throughput was achieved. Maximizing Retiring typically increases the Instructions-per-cycle (see tma_info_thread_ipc metric). Note that a high Retiring value does not necessary mean there is no room for more performance. For example; Heavy-operations or Microcode Assists are categorized under Retiring. They often indicate suboptimal performance and can often be optimized or avoided. ", + "BriefDescription": "This category represents fraction of slots utilized by useful work i.e. issued uops that eventually get retired. Ideally; all pipeline slots would be attributed to the Retiring category. Retiring of 100% would indicate the maximum Pipeline_Width throughput was achieved. Maximizing Retiring typically increases the Instructions-per-cycle (see IPC metric). Note that a high Retiring value does not necessary mean there is no room for more performance. For example; Heavy-operations or Microcode Assists are categorized under Retiring. They often indicate suboptimal performance and can often be optimized or avoided. ", "UnitOfMeasure": "percent", "Events": [ { diff --git a/ARL/metrics/perf/arrowlake_metrics_lioncove_core_perf.json b/ARL/metrics/perf/arrowlake_metrics_lioncove_core_perf.json index e858ca88..52e88c79 100644 --- a/ARL/metrics/perf/arrowlake_metrics_lioncove_core_perf.json +++ b/ARL/metrics/perf/arrowlake_metrics_lioncove_core_perf.json @@ -843,7 +843,7 @@ "MetricName": "tma_retiring", "ScaleUnit": "100%", "MetricThreshold": "tma_retiring > 0.7 | tma_heavy_operations > 0.1", - "PublicDescription": "This category represents fraction of slots utilized by useful work i.e. issued uops that eventually get retired. Ideally; all pipeline slots would be attributed to the Retiring category. Retiring of 100% would indicate the maximum Pipeline_Width throughput was achieved. Maximizing Retiring typically increases the Instructions-per-cycle (see tma_info_thread_ipc metric). Note that a high Retiring value does not necessary mean there is no room for more performance. For example; Heavy-operations or Microcode Assists are categorized under Retiring. They often indicate suboptimal performance and can often be optimized or avoided. Sample with: UOPS_RETIRED.SLOTS.", + "PublicDescription": "This category represents fraction of slots utilized by useful work i.e. issued uops that eventually get retired. Ideally; all pipeline slots would be attributed to the Retiring category. Retiring of 100% would indicate the maximum Pipeline_Width throughput was achieved. Maximizing Retiring typically increases the Instructions-per-cycle (see IPC metric). Note that a high Retiring value does not necessary mean there is no room for more performance. For example; Heavy-operations or Microcode Assists are categorized under Retiring. They often indicate suboptimal performance and can often be optimized or avoided. Sample with: UOPS_RETIRED.SLOTS.", "DefaultMetricgroupName": "TopdownL1", "MetricGroupnoGroup": "TopdownL1;Default" }, diff --git a/BDW/metrics/broadwell_metrics.json b/BDW/metrics/broadwell_metrics.json index 25f2586e..6d835b98 100644 --- a/BDW/metrics/broadwell_metrics.json +++ b/BDW/metrics/broadwell_metrics.json @@ -3410,7 +3410,7 @@ "MetricName": "Retiring", "LegacyName": "metric_TMA_Retiring(%)", "Level": 1, - "BriefDescription": "This category represents fraction of slots utilized by useful work i.e. issued uops that eventually get retired. Ideally; all pipeline slots would be attributed to the Retiring category. Retiring of 100% would indicate the maximum Pipeline_Width throughput was achieved. Maximizing Retiring typically increases the Instructions-per-cycle (see tma_info_thread_ipc metric). Note that a high Retiring value does not necessary mean there is no room for more performance. For example; Heavy-operations or Microcode Assists are categorized under Retiring. They often indicate suboptimal performance and can often be optimized or avoided. ", + "BriefDescription": "This category represents fraction of slots utilized by useful work i.e. issued uops that eventually get retired. Ideally; all pipeline slots would be attributed to the Retiring category. Retiring of 100% would indicate the maximum Pipeline_Width throughput was achieved. Maximizing Retiring typically increases the Instructions-per-cycle (see IPC metric). Note that a high Retiring value does not necessary mean there is no room for more performance. For example; Heavy-operations or Microcode Assists are categorized under Retiring. They often indicate suboptimal performance and can often be optimized or avoided. ", "UnitOfMeasure": "percent", "Events": [ { diff --git a/BDW/metrics/perf/broadwell_metrics_perf.json b/BDW/metrics/perf/broadwell_metrics_perf.json index 945af533..081eea0b 100644 --- a/BDW/metrics/perf/broadwell_metrics_perf.json +++ b/BDW/metrics/perf/broadwell_metrics_perf.json @@ -523,7 +523,7 @@ "MetricName": "tma_retiring", "ScaleUnit": "100%", "MetricThreshold": "tma_retiring > 0.7 | tma_heavy_operations > 0.1", - "PublicDescription": "This category represents fraction of slots utilized by useful work i.e. issued uops that eventually get retired. Ideally; all pipeline slots would be attributed to the Retiring category. Retiring of 100% would indicate the maximum Pipeline_Width throughput was achieved. Maximizing Retiring typically increases the Instructions-per-cycle (see tma_info_thread_ipc metric). Note that a high Retiring value does not necessary mean there is no room for more performance. For example; Heavy-operations or Microcode Assists are categorized under Retiring. They often indicate suboptimal performance and can often be optimized or avoided. Sample with: UOPS_RETIRED.RETIRE_SLOTS." + "PublicDescription": "This category represents fraction of slots utilized by useful work i.e. issued uops that eventually get retired. Ideally; all pipeline slots would be attributed to the Retiring category. Retiring of 100% would indicate the maximum Pipeline_Width throughput was achieved. Maximizing Retiring typically increases the Instructions-per-cycle (see IPC metric). Note that a high Retiring value does not necessary mean there is no room for more performance. For example; Heavy-operations or Microcode Assists are categorized under Retiring. They often indicate suboptimal performance and can often be optimized or avoided. Sample with: UOPS_RETIRED.RETIRE_SLOTS." }, { "BriefDescription": "This metric represents fraction of slots where the CPU was retiring light-weight operations , instructions that require no more than one uop (micro-operation)", diff --git a/BDX/metrics/broadwellx_metrics.json b/BDX/metrics/broadwellx_metrics.json index 78fe710d..eb8fcff1 100644 --- a/BDX/metrics/broadwellx_metrics.json +++ b/BDX/metrics/broadwellx_metrics.json @@ -4472,7 +4472,7 @@ "MetricName": "Retiring", "LegacyName": "metric_TMA_Retiring(%)", "Level": 1, - "BriefDescription": "This category represents fraction of slots utilized by useful work i.e. issued uops that eventually get retired. Ideally; all pipeline slots would be attributed to the Retiring category. Retiring of 100% would indicate the maximum Pipeline_Width throughput was achieved. Maximizing Retiring typically increases the Instructions-per-cycle (see tma_info_thread_ipc metric). Note that a high Retiring value does not necessary mean there is no room for more performance. For example; Heavy-operations or Microcode Assists are categorized under Retiring. They often indicate suboptimal performance and can often be optimized or avoided. ", + "BriefDescription": "This category represents fraction of slots utilized by useful work i.e. issued uops that eventually get retired. Ideally; all pipeline slots would be attributed to the Retiring category. Retiring of 100% would indicate the maximum Pipeline_Width throughput was achieved. Maximizing Retiring typically increases the Instructions-per-cycle (see IPC metric). Note that a high Retiring value does not necessary mean there is no room for more performance. For example; Heavy-operations or Microcode Assists are categorized under Retiring. They often indicate suboptimal performance and can often be optimized or avoided. ", "UnitOfMeasure": "percent", "Events": [ { diff --git a/BDX/metrics/perf/broadwellx_metrics_perf.json b/BDX/metrics/perf/broadwellx_metrics_perf.json index c3db4c8a..4c0d4bbd 100644 --- a/BDX/metrics/perf/broadwellx_metrics_perf.json +++ b/BDX/metrics/perf/broadwellx_metrics_perf.json @@ -792,7 +792,7 @@ "MetricName": "tma_retiring", "ScaleUnit": "100%", "MetricThreshold": "tma_retiring > 0.7 | tma_heavy_operations > 0.1", - "PublicDescription": "This category represents fraction of slots utilized by useful work i.e. issued uops that eventually get retired. Ideally; all pipeline slots would be attributed to the Retiring category. Retiring of 100% would indicate the maximum Pipeline_Width throughput was achieved. Maximizing Retiring typically increases the Instructions-per-cycle (see tma_info_thread_ipc metric). Note that a high Retiring value does not necessary mean there is no room for more performance. For example; Heavy-operations or Microcode Assists are categorized under Retiring. They often indicate suboptimal performance and can often be optimized or avoided. Sample with: UOPS_RETIRED.RETIRE_SLOTS." + "PublicDescription": "This category represents fraction of slots utilized by useful work i.e. issued uops that eventually get retired. Ideally; all pipeline slots would be attributed to the Retiring category. Retiring of 100% would indicate the maximum Pipeline_Width throughput was achieved. Maximizing Retiring typically increases the Instructions-per-cycle (see IPC metric). Note that a high Retiring value does not necessary mean there is no room for more performance. For example; Heavy-operations or Microcode Assists are categorized under Retiring. They often indicate suboptimal performance and can often be optimized or avoided. Sample with: UOPS_RETIRED.RETIRE_SLOTS." }, { "BriefDescription": "This metric represents fraction of slots where the CPU was retiring light-weight operations , instructions that require no more than one uop (micro-operation)", diff --git a/CLX/metrics/cascadelakex_metrics.json b/CLX/metrics/cascadelakex_metrics.json index 01cca6c9..a582e337 100644 --- a/CLX/metrics/cascadelakex_metrics.json +++ b/CLX/metrics/cascadelakex_metrics.json @@ -8050,7 +8050,7 @@ "MetricName": "Retiring", "LegacyName": "metric_TMA_Retiring(%)", "Level": 1, - "BriefDescription": "This category represents fraction of slots utilized by useful work i.e. issued uops that eventually get retired. Ideally; all pipeline slots would be attributed to the Retiring category. Retiring of 100% would indicate the maximum Pipeline_Width throughput was achieved. Maximizing Retiring typically increases the Instructions-per-cycle (see tma_info_thread_ipc metric). Note that a high Retiring value does not necessary mean there is no room for more performance. For example; Heavy-operations or Microcode Assists are categorized under Retiring. They often indicate suboptimal performance and can often be optimized or avoided. ", + "BriefDescription": "This category represents fraction of slots utilized by useful work i.e. issued uops that eventually get retired. Ideally; all pipeline slots would be attributed to the Retiring category. Retiring of 100% would indicate the maximum Pipeline_Width throughput was achieved. Maximizing Retiring typically increases the Instructions-per-cycle (see IPC metric). Note that a high Retiring value does not necessary mean there is no room for more performance. For example; Heavy-operations or Microcode Assists are categorized under Retiring. They often indicate suboptimal performance and can often be optimized or avoided. ", "UnitOfMeasure": "percent", "Events": [ { diff --git a/CLX/metrics/perf/cascadelakex_metrics_perf.json b/CLX/metrics/perf/cascadelakex_metrics_perf.json index 0d9cc7d7..4a7d56bc 100644 --- a/CLX/metrics/perf/cascadelakex_metrics_perf.json +++ b/CLX/metrics/perf/cascadelakex_metrics_perf.json @@ -1125,7 +1125,7 @@ "MetricName": "tma_retiring", "ScaleUnit": "100%", "MetricThreshold": "tma_retiring > 0.7 | tma_heavy_operations > 0.1", - "PublicDescription": "This category represents fraction of slots utilized by useful work i.e. issued uops that eventually get retired. Ideally; all pipeline slots would be attributed to the Retiring category. Retiring of 100% would indicate the maximum Pipeline_Width throughput was achieved. Maximizing Retiring typically increases the Instructions-per-cycle (see tma_info_thread_ipc metric). Note that a high Retiring value does not necessary mean there is no room for more performance. For example; Heavy-operations or Microcode Assists are categorized under Retiring. They often indicate suboptimal performance and can often be optimized or avoided. Sample with: UOPS_RETIRED.RETIRE_SLOTS." + "PublicDescription": "This category represents fraction of slots utilized by useful work i.e. issued uops that eventually get retired. Ideally; all pipeline slots would be attributed to the Retiring category. Retiring of 100% would indicate the maximum Pipeline_Width throughput was achieved. Maximizing Retiring typically increases the Instructions-per-cycle (see IPC metric). Note that a high Retiring value does not necessary mean there is no room for more performance. For example; Heavy-operations or Microcode Assists are categorized under Retiring. They often indicate suboptimal performance and can often be optimized or avoided. Sample with: UOPS_RETIRED.RETIRE_SLOTS." }, { "BriefDescription": "This metric represents fraction of slots where the CPU was retiring light-weight operations , instructions that require no more than one uop (micro-operation)", diff --git a/EMR/metrics/emeraldrapids_metrics.json b/EMR/metrics/emeraldrapids_metrics.json index 97b634ea..e0f9b3fe 100644 --- a/EMR/metrics/emeraldrapids_metrics.json +++ b/EMR/metrics/emeraldrapids_metrics.json @@ -8194,7 +8194,7 @@ "MetricName": "Retiring", "LegacyName": "metric_TMA_Retiring(%)", "Level": 1, - "BriefDescription": "This category represents fraction of slots utilized by useful work i.e. issued uops that eventually get retired. Ideally; all pipeline slots would be attributed to the Retiring category. Retiring of 100% would indicate the maximum Pipeline_Width throughput was achieved. Maximizing Retiring typically increases the Instructions-per-cycle (see tma_info_thread_ipc metric). Note that a high Retiring value does not necessary mean there is no room for more performance. For example; Heavy-operations or Microcode Assists are categorized under Retiring. They often indicate suboptimal performance and can often be optimized or avoided. ", + "BriefDescription": "This category represents fraction of slots utilized by useful work i.e. issued uops that eventually get retired. Ideally; all pipeline slots would be attributed to the Retiring category. Retiring of 100% would indicate the maximum Pipeline_Width throughput was achieved. Maximizing Retiring typically increases the Instructions-per-cycle (see IPC metric). Note that a high Retiring value does not necessary mean there is no room for more performance. For example; Heavy-operations or Microcode Assists are categorized under Retiring. They often indicate suboptimal performance and can often be optimized or avoided. ", "UnitOfMeasure": "percent", "Events": [ { diff --git a/EMR/metrics/perf/emeraldrapids_metrics_perf.json b/EMR/metrics/perf/emeraldrapids_metrics_perf.json index 335b88b1..1881a862 100644 --- a/EMR/metrics/perf/emeraldrapids_metrics_perf.json +++ b/EMR/metrics/perf/emeraldrapids_metrics_perf.json @@ -1212,7 +1212,7 @@ "MetricName": "tma_retiring", "ScaleUnit": "100%", "MetricThreshold": "tma_retiring > 0.7 | tma_heavy_operations > 0.1", - "PublicDescription": "This category represents fraction of slots utilized by useful work i.e. issued uops that eventually get retired. Ideally; all pipeline slots would be attributed to the Retiring category. Retiring of 100% would indicate the maximum Pipeline_Width throughput was achieved. Maximizing Retiring typically increases the Instructions-per-cycle (see tma_info_thread_ipc metric). Note that a high Retiring value does not necessary mean there is no room for more performance. For example; Heavy-operations or Microcode Assists are categorized under Retiring. They often indicate suboptimal performance and can often be optimized or avoided. Sample with: UOPS_RETIRED.SLOTS.", + "PublicDescription": "This category represents fraction of slots utilized by useful work i.e. issued uops that eventually get retired. Ideally; all pipeline slots would be attributed to the Retiring category. Retiring of 100% would indicate the maximum Pipeline_Width throughput was achieved. Maximizing Retiring typically increases the Instructions-per-cycle (see IPC metric). Note that a high Retiring value does not necessary mean there is no room for more performance. For example; Heavy-operations or Microcode Assists are categorized under Retiring. They often indicate suboptimal performance and can often be optimized or avoided. Sample with: UOPS_RETIRED.SLOTS.", "DefaultMetricgroupName": "TopdownL1", "MetricGroupnoGroup": "TopdownL1;Default" }, diff --git a/GNR/metrics/graniterapids_metrics.json b/GNR/metrics/graniterapids_metrics.json index e171999a..b046c378 100644 --- a/GNR/metrics/graniterapids_metrics.json +++ b/GNR/metrics/graniterapids_metrics.json @@ -8628,7 +8628,7 @@ "MetricName": "Retiring", "LegacyName": "metric_TMA_Retiring(%)", "Level": 1, - "BriefDescription": "This category represents fraction of slots utilized by useful work i.e. issued uops that eventually get retired. Ideally; all pipeline slots would be attributed to the Retiring category. Retiring of 100% would indicate the maximum Pipeline_Width throughput was achieved. Maximizing Retiring typically increases the Instructions-per-cycle (see tma_info_thread_ipc metric). Note that a high Retiring value does not necessary mean there is no room for more performance. For example; Heavy-operations or Microcode Assists are categorized under Retiring. They often indicate suboptimal performance and can often be optimized or avoided. ", + "BriefDescription": "This category represents fraction of slots utilized by useful work i.e. issued uops that eventually get retired. Ideally; all pipeline slots would be attributed to the Retiring category. Retiring of 100% would indicate the maximum Pipeline_Width throughput was achieved. Maximizing Retiring typically increases the Instructions-per-cycle (see IPC metric). Note that a high Retiring value does not necessary mean there is no room for more performance. For example; Heavy-operations or Microcode Assists are categorized under Retiring. They often indicate suboptimal performance and can often be optimized or avoided. ", "UnitOfMeasure": "percent", "Events": [ { diff --git a/GNR/metrics/perf/graniterapids_metrics_perf.json b/GNR/metrics/perf/graniterapids_metrics_perf.json index 0cf335e7..de9b48c2 100644 --- a/GNR/metrics/perf/graniterapids_metrics_perf.json +++ b/GNR/metrics/perf/graniterapids_metrics_perf.json @@ -1269,7 +1269,7 @@ "MetricName": "tma_retiring", "ScaleUnit": "100%", "MetricThreshold": "tma_retiring > 0.7 | tma_heavy_operations > 0.1", - "PublicDescription": "This category represents fraction of slots utilized by useful work i.e. issued uops that eventually get retired. Ideally; all pipeline slots would be attributed to the Retiring category. Retiring of 100% would indicate the maximum Pipeline_Width throughput was achieved. Maximizing Retiring typically increases the Instructions-per-cycle (see tma_info_thread_ipc metric). Note that a high Retiring value does not necessary mean there is no room for more performance. For example; Heavy-operations or Microcode Assists are categorized under Retiring. They often indicate suboptimal performance and can often be optimized or avoided. Sample with: UOPS_RETIRED.SLOTS.", + "PublicDescription": "This category represents fraction of slots utilized by useful work i.e. issued uops that eventually get retired. Ideally; all pipeline slots would be attributed to the Retiring category. Retiring of 100% would indicate the maximum Pipeline_Width throughput was achieved. Maximizing Retiring typically increases the Instructions-per-cycle (see IPC metric). Note that a high Retiring value does not necessary mean there is no room for more performance. For example; Heavy-operations or Microcode Assists are categorized under Retiring. They often indicate suboptimal performance and can often be optimized or avoided. Sample with: UOPS_RETIRED.SLOTS.", "DefaultMetricgroupName": "TopdownL1", "MetricGroupnoGroup": "TopdownL1;Default" }, diff --git a/HSW/metrics/haswell_metrics.json b/HSW/metrics/haswell_metrics.json index 423bfdeb..f13b5888 100644 --- a/HSW/metrics/haswell_metrics.json +++ b/HSW/metrics/haswell_metrics.json @@ -2419,7 +2419,7 @@ "MetricName": "Retiring", "LegacyName": "metric_TMA_Retiring(%)", "Level": 1, - "BriefDescription": "This category represents fraction of slots utilized by useful work i.e. issued uops that eventually get retired. Ideally; all pipeline slots would be attributed to the Retiring category. Retiring of 100% would indicate the maximum Pipeline_Width throughput was achieved. Maximizing Retiring typically increases the Instructions-per-cycle (see tma_info_thread_ipc metric). Note that a high Retiring value does not necessary mean there is no room for more performance. For example; Heavy-operations or Microcode Assists are categorized under Retiring. They often indicate suboptimal performance and can often be optimized or avoided. ", + "BriefDescription": "This category represents fraction of slots utilized by useful work i.e. issued uops that eventually get retired. Ideally; all pipeline slots would be attributed to the Retiring category. Retiring of 100% would indicate the maximum Pipeline_Width throughput was achieved. Maximizing Retiring typically increases the Instructions-per-cycle (see IPC metric). Note that a high Retiring value does not necessary mean there is no room for more performance. For example; Heavy-operations or Microcode Assists are categorized under Retiring. They often indicate suboptimal performance and can often be optimized or avoided. ", "UnitOfMeasure": "percent", "Events": [ { diff --git a/HSW/metrics/perf/haswell_metrics_perf.json b/HSW/metrics/perf/haswell_metrics_perf.json index 80ffcac3..ea9530ac 100644 --- a/HSW/metrics/perf/haswell_metrics_perf.json +++ b/HSW/metrics/perf/haswell_metrics_perf.json @@ -495,7 +495,7 @@ "MetricName": "tma_retiring", "ScaleUnit": "100%", "MetricThreshold": "tma_retiring > 70 | tma_heavy_operations > 10", - "PublicDescription": "This category represents fraction of slots utilized by useful work i.e. issued uops that eventually get retired. Ideally; all pipeline slots would be attributed to the Retiring category. Retiring of 100% would indicate the maximum Pipeline_Width throughput was achieved. Maximizing Retiring typically increases the Instructions-per-cycle (see tma_info_thread_ipc metric). Note that a high Retiring value does not necessary mean there is no room for more performance. For example; Heavy-operations or Microcode Assists are categorized under Retiring. They often indicate suboptimal performance and can often be optimized or avoided. Sample with: UOPS_RETIRED.RETIRE_SLOTS." + "PublicDescription": "This category represents fraction of slots utilized by useful work i.e. issued uops that eventually get retired. Ideally; all pipeline slots would be attributed to the Retiring category. Retiring of 100% would indicate the maximum Pipeline_Width throughput was achieved. Maximizing Retiring typically increases the Instructions-per-cycle (see IPC metric). Note that a high Retiring value does not necessary mean there is no room for more performance. For example; Heavy-operations or Microcode Assists are categorized under Retiring. They often indicate suboptimal performance and can often be optimized or avoided. Sample with: UOPS_RETIRED.RETIRE_SLOTS." }, { "BriefDescription": "This metric represents fraction of slots where the CPU was retiring light-weight operations , instructions that require no more than one uop (micro-operation)", diff --git a/HSX/metrics/haswellx_metrics.json b/HSX/metrics/haswellx_metrics.json index 17673c46..79e8de14 100644 --- a/HSX/metrics/haswellx_metrics.json +++ b/HSX/metrics/haswellx_metrics.json @@ -4273,7 +4273,7 @@ "MetricName": "Retiring", "LegacyName": "metric_TMA_Retiring(%)", "Level": 1, - "BriefDescription": "This category represents fraction of slots utilized by useful work i.e. issued uops that eventually get retired. Ideally; all pipeline slots would be attributed to the Retiring category. Retiring of 100% would indicate the maximum Pipeline_Width throughput was achieved. Maximizing Retiring typically increases the Instructions-per-cycle (see tma_info_thread_ipc metric). Note that a high Retiring value does not necessary mean there is no room for more performance. For example; Heavy-operations or Microcode Assists are categorized under Retiring. They often indicate suboptimal performance and can often be optimized or avoided. ", + "BriefDescription": "This category represents fraction of slots utilized by useful work i.e. issued uops that eventually get retired. Ideally; all pipeline slots would be attributed to the Retiring category. Retiring of 100% would indicate the maximum Pipeline_Width throughput was achieved. Maximizing Retiring typically increases the Instructions-per-cycle (see IPC metric). Note that a high Retiring value does not necessary mean there is no room for more performance. For example; Heavy-operations or Microcode Assists are categorized under Retiring. They often indicate suboptimal performance and can often be optimized or avoided. ", "UnitOfMeasure": "percent", "Events": [ { diff --git a/HSX/metrics/perf/haswellx_metrics_perf.json b/HSX/metrics/perf/haswellx_metrics_perf.json index 748ef508..17021af0 100644 --- a/HSX/metrics/perf/haswellx_metrics_perf.json +++ b/HSX/metrics/perf/haswellx_metrics_perf.json @@ -765,7 +765,7 @@ "MetricName": "tma_retiring", "ScaleUnit": "100%", "MetricThreshold": "tma_retiring > 0.7 | tma_heavy_operations > 0.1", - "PublicDescription": "This category represents fraction of slots utilized by useful work i.e. issued uops that eventually get retired. Ideally; all pipeline slots would be attributed to the Retiring category. Retiring of 100% would indicate the maximum Pipeline_Width throughput was achieved. Maximizing Retiring typically increases the Instructions-per-cycle (see tma_info_thread_ipc metric). Note that a high Retiring value does not necessary mean there is no room for more performance. For example; Heavy-operations or Microcode Assists are categorized under Retiring. They often indicate suboptimal performance and can often be optimized or avoided. Sample with: UOPS_RETIRED.RETIRE_SLOTS." + "PublicDescription": "This category represents fraction of slots utilized by useful work i.e. issued uops that eventually get retired. Ideally; all pipeline slots would be attributed to the Retiring category. Retiring of 100% would indicate the maximum Pipeline_Width throughput was achieved. Maximizing Retiring typically increases the Instructions-per-cycle (see IPC metric). Note that a high Retiring value does not necessary mean there is no room for more performance. For example; Heavy-operations or Microcode Assists are categorized under Retiring. They often indicate suboptimal performance and can often be optimized or avoided. Sample with: UOPS_RETIRED.RETIRE_SLOTS." }, { "BriefDescription": "This metric represents fraction of slots where the CPU was retiring light-weight operations , instructions that require no more than one uop (micro-operation)", diff --git a/ICL/metrics/icelake_metrics.json b/ICL/metrics/icelake_metrics.json index f1705a0a..5e450357 100644 --- a/ICL/metrics/icelake_metrics.json +++ b/ICL/metrics/icelake_metrics.json @@ -6898,7 +6898,7 @@ "MetricName": "Retiring", "LegacyName": "metric_TMA_Retiring(%)", "Level": 1, - "BriefDescription": "This category represents fraction of slots utilized by useful work i.e. issued uops that eventually get retired. Ideally; all pipeline slots would be attributed to the Retiring category. Retiring of 100% would indicate the maximum Pipeline_Width throughput was achieved. Maximizing Retiring typically increases the Instructions-per-cycle (see tma_info_thread_ipc metric). Note that a high Retiring value does not necessary mean there is no room for more performance. For example; Heavy-operations or Microcode Assists are categorized under Retiring. They often indicate suboptimal performance and can often be optimized or avoided. ", + "BriefDescription": "This category represents fraction of slots utilized by useful work i.e. issued uops that eventually get retired. Ideally; all pipeline slots would be attributed to the Retiring category. Retiring of 100% would indicate the maximum Pipeline_Width throughput was achieved. Maximizing Retiring typically increases the Instructions-per-cycle (see IPC metric). Note that a high Retiring value does not necessary mean there is no room for more performance. For example; Heavy-operations or Microcode Assists are categorized under Retiring. They often indicate suboptimal performance and can often be optimized or avoided. ", "UnitOfMeasure": "percent", "Events": [ { diff --git a/ICL/metrics/perf/icelake_metrics_perf.json b/ICL/metrics/perf/icelake_metrics_perf.json index 592e3a3a..6296af84 100644 --- a/ICL/metrics/perf/icelake_metrics_perf.json +++ b/ICL/metrics/perf/icelake_metrics_perf.json @@ -868,7 +868,7 @@ "MetricName": "tma_retiring", "ScaleUnit": "100%", "MetricThreshold": "tma_retiring > 0.7 | tma_heavy_operations > 0.1", - "PublicDescription": "This category represents fraction of slots utilized by useful work i.e. issued uops that eventually get retired. Ideally; all pipeline slots would be attributed to the Retiring category. Retiring of 100% would indicate the maximum Pipeline_Width throughput was achieved. Maximizing Retiring typically increases the Instructions-per-cycle (see tma_info_thread_ipc metric). Note that a high Retiring value does not necessary mean there is no room for more performance. For example; Heavy-operations or Microcode Assists are categorized under Retiring. They often indicate suboptimal performance and can often be optimized or avoided. Sample with: UOPS_RETIRED.SLOTS.", + "PublicDescription": "This category represents fraction of slots utilized by useful work i.e. issued uops that eventually get retired. Ideally; all pipeline slots would be attributed to the Retiring category. Retiring of 100% would indicate the maximum Pipeline_Width throughput was achieved. Maximizing Retiring typically increases the Instructions-per-cycle (see IPC metric). Note that a high Retiring value does not necessary mean there is no room for more performance. For example; Heavy-operations or Microcode Assists are categorized under Retiring. They often indicate suboptimal performance and can often be optimized or avoided. Sample with: UOPS_RETIRED.SLOTS.", "DefaultMetricgroupName": "TopdownL1", "MetricGroupnoGroup": "TopdownL1;Default" }, diff --git a/ICX/metrics/icelakex_metrics.json b/ICX/metrics/icelakex_metrics.json index 184bf698..e5dd5196 100644 --- a/ICX/metrics/icelakex_metrics.json +++ b/ICX/metrics/icelakex_metrics.json @@ -8274,7 +8274,7 @@ "MetricName": "Retiring", "LegacyName": "metric_TMA_Retiring(%)", "Level": 1, - "BriefDescription": "This category represents fraction of slots utilized by useful work i.e. issued uops that eventually get retired. Ideally; all pipeline slots would be attributed to the Retiring category. Retiring of 100% would indicate the maximum Pipeline_Width throughput was achieved. Maximizing Retiring typically increases the Instructions-per-cycle (see tma_info_thread_ipc metric). Note that a high Retiring value does not necessary mean there is no room for more performance. For example; Heavy-operations or Microcode Assists are categorized under Retiring. They often indicate suboptimal performance and can often be optimized or avoided. ", + "BriefDescription": "This category represents fraction of slots utilized by useful work i.e. issued uops that eventually get retired. Ideally; all pipeline slots would be attributed to the Retiring category. Retiring of 100% would indicate the maximum Pipeline_Width throughput was achieved. Maximizing Retiring typically increases the Instructions-per-cycle (see IPC metric). Note that a high Retiring value does not necessary mean there is no room for more performance. For example; Heavy-operations or Microcode Assists are categorized under Retiring. They often indicate suboptimal performance and can often be optimized or avoided. ", "UnitOfMeasure": "percent", "Events": [ { diff --git a/ICX/metrics/perf/icelakex_metrics_perf.json b/ICX/metrics/perf/icelakex_metrics_perf.json index 4f9ad331..71820246 100644 --- a/ICX/metrics/perf/icelakex_metrics_perf.json +++ b/ICX/metrics/perf/icelakex_metrics_perf.json @@ -1234,7 +1234,7 @@ "MetricName": "tma_retiring", "ScaleUnit": "100%", "MetricThreshold": "tma_retiring > 0.7 | tma_heavy_operations > 0.1", - "PublicDescription": "This category represents fraction of slots utilized by useful work i.e. issued uops that eventually get retired. Ideally; all pipeline slots would be attributed to the Retiring category. Retiring of 100% would indicate the maximum Pipeline_Width throughput was achieved. Maximizing Retiring typically increases the Instructions-per-cycle (see tma_info_thread_ipc metric). Note that a high Retiring value does not necessary mean there is no room for more performance. For example; Heavy-operations or Microcode Assists are categorized under Retiring. They often indicate suboptimal performance and can often be optimized or avoided. Sample with: UOPS_RETIRED.SLOTS.", + "PublicDescription": "This category represents fraction of slots utilized by useful work i.e. issued uops that eventually get retired. Ideally; all pipeline slots would be attributed to the Retiring category. Retiring of 100% would indicate the maximum Pipeline_Width throughput was achieved. Maximizing Retiring typically increases the Instructions-per-cycle (see IPC metric). Note that a high Retiring value does not necessary mean there is no room for more performance. For example; Heavy-operations or Microcode Assists are categorized under Retiring. They often indicate suboptimal performance and can often be optimized or avoided. Sample with: UOPS_RETIRED.SLOTS.", "DefaultMetricgroupName": "TopdownL1", "MetricGroupnoGroup": "TopdownL1;Default" }, diff --git a/LNL/metrics/lunarlake_metrics_lioncove_core.json b/LNL/metrics/lunarlake_metrics_lioncove_core.json index 44c2717a..1bf83847 100644 --- a/LNL/metrics/lunarlake_metrics_lioncove_core.json +++ b/LNL/metrics/lunarlake_metrics_lioncove_core.json @@ -6655,7 +6655,7 @@ "MetricName": "Retiring", "LegacyName": "metric_TMA_Retiring(%)", "Level": 1, - "BriefDescription": "This category represents fraction of slots utilized by useful work i.e. issued uops that eventually get retired. Ideally; all pipeline slots would be attributed to the Retiring category. Retiring of 100% would indicate the maximum Pipeline_Width throughput was achieved. Maximizing Retiring typically increases the Instructions-per-cycle (see tma_info_thread_ipc metric). Note that a high Retiring value does not necessary mean there is no room for more performance. For example; Heavy-operations or Microcode Assists are categorized under Retiring. They often indicate suboptimal performance and can often be optimized or avoided. ", + "BriefDescription": "This category represents fraction of slots utilized by useful work i.e. issued uops that eventually get retired. Ideally; all pipeline slots would be attributed to the Retiring category. Retiring of 100% would indicate the maximum Pipeline_Width throughput was achieved. Maximizing Retiring typically increases the Instructions-per-cycle (see IPC metric). Note that a high Retiring value does not necessary mean there is no room for more performance. For example; Heavy-operations or Microcode Assists are categorized under Retiring. They often indicate suboptimal performance and can often be optimized or avoided. ", "UnitOfMeasure": "percent", "Events": [ { diff --git a/LNL/metrics/perf/lunarlake_metrics_lioncove_core_perf.json b/LNL/metrics/perf/lunarlake_metrics_lioncove_core_perf.json index 3ca5c1ce..ed9bd849 100644 --- a/LNL/metrics/perf/lunarlake_metrics_lioncove_core_perf.json +++ b/LNL/metrics/perf/lunarlake_metrics_lioncove_core_perf.json @@ -892,7 +892,7 @@ "MetricName": "tma_retiring", "ScaleUnit": "100%", "MetricThreshold": "tma_retiring > 0.7 | tma_heavy_operations > 0.1", - "PublicDescription": "This category represents fraction of slots utilized by useful work i.e. issued uops that eventually get retired. Ideally; all pipeline slots would be attributed to the Retiring category. Retiring of 100% would indicate the maximum Pipeline_Width throughput was achieved. Maximizing Retiring typically increases the Instructions-per-cycle (see tma_info_thread_ipc metric). Note that a high Retiring value does not necessary mean there is no room for more performance. For example; Heavy-operations or Microcode Assists are categorized under Retiring. They often indicate suboptimal performance and can often be optimized or avoided. Sample with: UOPS_RETIRED.SLOTS.", + "PublicDescription": "This category represents fraction of slots utilized by useful work i.e. issued uops that eventually get retired. Ideally; all pipeline slots would be attributed to the Retiring category. Retiring of 100% would indicate the maximum Pipeline_Width throughput was achieved. Maximizing Retiring typically increases the Instructions-per-cycle (see IPC metric). Note that a high Retiring value does not necessary mean there is no room for more performance. For example; Heavy-operations or Microcode Assists are categorized under Retiring. They often indicate suboptimal performance and can often be optimized or avoided. Sample with: UOPS_RETIRED.SLOTS.", "DefaultMetricgroupName": "TopdownL1", "MetricGroupnoGroup": "TopdownL1;Default" }, diff --git a/MTL/metrics/meteorlake_metrics_redwoodcove_core.json b/MTL/metrics/meteorlake_metrics_redwoodcove_core.json index 3985d797..6fd57804 100644 --- a/MTL/metrics/meteorlake_metrics_redwoodcove_core.json +++ b/MTL/metrics/meteorlake_metrics_redwoodcove_core.json @@ -7221,7 +7221,7 @@ "MetricName": "Retiring", "LegacyName": "metric_TMA_Retiring(%)", "Level": 1, - "BriefDescription": "This category represents fraction of slots utilized by useful work i.e. issued uops that eventually get retired. Ideally; all pipeline slots would be attributed to the Retiring category. Retiring of 100% would indicate the maximum Pipeline_Width throughput was achieved. Maximizing Retiring typically increases the Instructions-per-cycle (see tma_info_thread_ipc metric). Note that a high Retiring value does not necessary mean there is no room for more performance. For example; Heavy-operations or Microcode Assists are categorized under Retiring. They often indicate suboptimal performance and can often be optimized or avoided. ", + "BriefDescription": "This category represents fraction of slots utilized by useful work i.e. issued uops that eventually get retired. Ideally; all pipeline slots would be attributed to the Retiring category. Retiring of 100% would indicate the maximum Pipeline_Width throughput was achieved. Maximizing Retiring typically increases the Instructions-per-cycle (see IPC metric). Note that a high Retiring value does not necessary mean there is no room for more performance. For example; Heavy-operations or Microcode Assists are categorized under Retiring. They often indicate suboptimal performance and can often be optimized or avoided. ", "UnitOfMeasure": "percent", "Events": [ { diff --git a/MTL/metrics/perf/meteorlake_metrics_redwoodcove_core_perf.json b/MTL/metrics/perf/meteorlake_metrics_redwoodcove_core_perf.json index d1d5e2c6..5816f05a 100644 --- a/MTL/metrics/perf/meteorlake_metrics_redwoodcove_core_perf.json +++ b/MTL/metrics/perf/meteorlake_metrics_redwoodcove_core_perf.json @@ -912,7 +912,7 @@ "MetricName": "tma_retiring", "ScaleUnit": "100%", "MetricThreshold": "tma_retiring > 0.7 | tma_heavy_operations > 0.1", - "PublicDescription": "This category represents fraction of slots utilized by useful work i.e. issued uops that eventually get retired. Ideally; all pipeline slots would be attributed to the Retiring category. Retiring of 100% would indicate the maximum Pipeline_Width throughput was achieved. Maximizing Retiring typically increases the Instructions-per-cycle (see tma_info_thread_ipc metric). Note that a high Retiring value does not necessary mean there is no room for more performance. For example; Heavy-operations or Microcode Assists are categorized under Retiring. They often indicate suboptimal performance and can often be optimized or avoided. Sample with: UOPS_RETIRED.SLOTS.", + "PublicDescription": "This category represents fraction of slots utilized by useful work i.e. issued uops that eventually get retired. Ideally; all pipeline slots would be attributed to the Retiring category. Retiring of 100% would indicate the maximum Pipeline_Width throughput was achieved. Maximizing Retiring typically increases the Instructions-per-cycle (see IPC metric). Note that a high Retiring value does not necessary mean there is no room for more performance. For example; Heavy-operations or Microcode Assists are categorized under Retiring. They often indicate suboptimal performance and can often be optimized or avoided. Sample with: UOPS_RETIRED.SLOTS.", "DefaultMetricgroupName": "TopdownL1", "MetricGroupnoGroup": "TopdownL1;Default" }, diff --git a/RKL/metrics/perf/rocketlake_metrics_perf.json b/RKL/metrics/perf/rocketlake_metrics_perf.json index 8d46e119..57f2da96 100644 --- a/RKL/metrics/perf/rocketlake_metrics_perf.json +++ b/RKL/metrics/perf/rocketlake_metrics_perf.json @@ -868,7 +868,7 @@ "MetricName": "tma_retiring", "ScaleUnit": "100%", "MetricThreshold": "tma_retiring > 0.7 | tma_heavy_operations > 0.1", - "PublicDescription": "This category represents fraction of slots utilized by useful work i.e. issued uops that eventually get retired. Ideally; all pipeline slots would be attributed to the Retiring category. Retiring of 100% would indicate the maximum Pipeline_Width throughput was achieved. Maximizing Retiring typically increases the Instructions-per-cycle (see tma_info_thread_ipc metric). Note that a high Retiring value does not necessary mean there is no room for more performance. For example; Heavy-operations or Microcode Assists are categorized under Retiring. They often indicate suboptimal performance and can often be optimized or avoided. Sample with: UOPS_RETIRED.SLOTS.", + "PublicDescription": "This category represents fraction of slots utilized by useful work i.e. issued uops that eventually get retired. Ideally; all pipeline slots would be attributed to the Retiring category. Retiring of 100% would indicate the maximum Pipeline_Width throughput was achieved. Maximizing Retiring typically increases the Instructions-per-cycle (see IPC metric). Note that a high Retiring value does not necessary mean there is no room for more performance. For example; Heavy-operations or Microcode Assists are categorized under Retiring. They often indicate suboptimal performance and can often be optimized or avoided. Sample with: UOPS_RETIRED.SLOTS.", "DefaultMetricgroupName": "TopdownL1", "MetricGroupnoGroup": "TopdownL1;Default" }, diff --git a/RKL/metrics/rocketlake_metrics.json b/RKL/metrics/rocketlake_metrics.json index acaf5c59..d7ec5ae3 100644 --- a/RKL/metrics/rocketlake_metrics.json +++ b/RKL/metrics/rocketlake_metrics.json @@ -6898,7 +6898,7 @@ "MetricName": "Retiring", "LegacyName": "metric_TMA_Retiring(%)", "Level": 1, - "BriefDescription": "This category represents fraction of slots utilized by useful work i.e. issued uops that eventually get retired. Ideally; all pipeline slots would be attributed to the Retiring category. Retiring of 100% would indicate the maximum Pipeline_Width throughput was achieved. Maximizing Retiring typically increases the Instructions-per-cycle (see tma_info_thread_ipc metric). Note that a high Retiring value does not necessary mean there is no room for more performance. For example; Heavy-operations or Microcode Assists are categorized under Retiring. They often indicate suboptimal performance and can often be optimized or avoided. ", + "BriefDescription": "This category represents fraction of slots utilized by useful work i.e. issued uops that eventually get retired. Ideally; all pipeline slots would be attributed to the Retiring category. Retiring of 100% would indicate the maximum Pipeline_Width throughput was achieved. Maximizing Retiring typically increases the Instructions-per-cycle (see IPC metric). Note that a high Retiring value does not necessary mean there is no room for more performance. For example; Heavy-operations or Microcode Assists are categorized under Retiring. They often indicate suboptimal performance and can often be optimized or avoided. ", "UnitOfMeasure": "percent", "Events": [ { diff --git a/SKL/metrics/perf/skylake_metrics_perf.json b/SKL/metrics/perf/skylake_metrics_perf.json index d381e260..c303b276 100644 --- a/SKL/metrics/perf/skylake_metrics_perf.json +++ b/SKL/metrics/perf/skylake_metrics_perf.json @@ -790,7 +790,7 @@ "MetricName": "tma_retiring", "ScaleUnit": "100%", "MetricThreshold": "tma_retiring > 0.7 | tma_heavy_operations > 0.1", - "PublicDescription": "This category represents fraction of slots utilized by useful work i.e. issued uops that eventually get retired. Ideally; all pipeline slots would be attributed to the Retiring category. Retiring of 100% would indicate the maximum Pipeline_Width throughput was achieved. Maximizing Retiring typically increases the Instructions-per-cycle (see tma_info_thread_ipc metric). Note that a high Retiring value does not necessary mean there is no room for more performance. For example; Heavy-operations or Microcode Assists are categorized under Retiring. They often indicate suboptimal performance and can often be optimized or avoided. Sample with: UOPS_RETIRED.RETIRE_SLOTS." + "PublicDescription": "This category represents fraction of slots utilized by useful work i.e. issued uops that eventually get retired. Ideally; all pipeline slots would be attributed to the Retiring category. Retiring of 100% would indicate the maximum Pipeline_Width throughput was achieved. Maximizing Retiring typically increases the Instructions-per-cycle (see IPC metric). Note that a high Retiring value does not necessary mean there is no room for more performance. For example; Heavy-operations or Microcode Assists are categorized under Retiring. They often indicate suboptimal performance and can often be optimized or avoided. Sample with: UOPS_RETIRED.RETIRE_SLOTS." }, { "BriefDescription": "This metric represents fraction of slots where the CPU was retiring light-weight operations , instructions that require no more than one uop (micro-operation)", diff --git a/SKL/metrics/skylake_metrics.json b/SKL/metrics/skylake_metrics.json index 8f46f345..047c8032 100644 --- a/SKL/metrics/skylake_metrics.json +++ b/SKL/metrics/skylake_metrics.json @@ -6692,7 +6692,7 @@ "MetricName": "Retiring", "LegacyName": "metric_TMA_Retiring(%)", "Level": 1, - "BriefDescription": "This category represents fraction of slots utilized by useful work i.e. issued uops that eventually get retired. Ideally; all pipeline slots would be attributed to the Retiring category. Retiring of 100% would indicate the maximum Pipeline_Width throughput was achieved. Maximizing Retiring typically increases the Instructions-per-cycle (see tma_info_thread_ipc metric). Note that a high Retiring value does not necessary mean there is no room for more performance. For example; Heavy-operations or Microcode Assists are categorized under Retiring. They often indicate suboptimal performance and can often be optimized or avoided. ", + "BriefDescription": "This category represents fraction of slots utilized by useful work i.e. issued uops that eventually get retired. Ideally; all pipeline slots would be attributed to the Retiring category. Retiring of 100% would indicate the maximum Pipeline_Width throughput was achieved. Maximizing Retiring typically increases the Instructions-per-cycle (see IPC metric). Note that a high Retiring value does not necessary mean there is no room for more performance. For example; Heavy-operations or Microcode Assists are categorized under Retiring. They often indicate suboptimal performance and can often be optimized or avoided. ", "UnitOfMeasure": "percent", "Events": [ { diff --git a/SKX/metrics/perf/skylakex_metrics_perf.json b/SKX/metrics/perf/skylakex_metrics_perf.json index 6a78ecf9..f93fb8c8 100644 --- a/SKX/metrics/perf/skylakex_metrics_perf.json +++ b/SKX/metrics/perf/skylakex_metrics_perf.json @@ -1095,7 +1095,7 @@ "MetricName": "tma_retiring", "ScaleUnit": "100%", "MetricThreshold": "tma_retiring > 0.7 | tma_heavy_operations > 0.1", - "PublicDescription": "This category represents fraction of slots utilized by useful work i.e. issued uops that eventually get retired. Ideally; all pipeline slots would be attributed to the Retiring category. Retiring of 100% would indicate the maximum Pipeline_Width throughput was achieved. Maximizing Retiring typically increases the Instructions-per-cycle (see tma_info_thread_ipc metric). Note that a high Retiring value does not necessary mean there is no room for more performance. For example; Heavy-operations or Microcode Assists are categorized under Retiring. They often indicate suboptimal performance and can often be optimized or avoided. Sample with: UOPS_RETIRED.RETIRE_SLOTS." + "PublicDescription": "This category represents fraction of slots utilized by useful work i.e. issued uops that eventually get retired. Ideally; all pipeline slots would be attributed to the Retiring category. Retiring of 100% would indicate the maximum Pipeline_Width throughput was achieved. Maximizing Retiring typically increases the Instructions-per-cycle (see IPC metric). Note that a high Retiring value does not necessary mean there is no room for more performance. For example; Heavy-operations or Microcode Assists are categorized under Retiring. They often indicate suboptimal performance and can often be optimized or avoided. Sample with: UOPS_RETIRED.RETIRE_SLOTS." }, { "BriefDescription": "This metric represents fraction of slots where the CPU was retiring light-weight operations , instructions that require no more than one uop (micro-operation)", diff --git a/SKX/metrics/skylakex_metrics.json b/SKX/metrics/skylakex_metrics.json index ca913f8f..1efc0036 100644 --- a/SKX/metrics/skylakex_metrics.json +++ b/SKX/metrics/skylakex_metrics.json @@ -7922,7 +7922,7 @@ "MetricName": "Retiring", "LegacyName": "metric_TMA_Retiring(%)", "Level": 1, - "BriefDescription": "This category represents fraction of slots utilized by useful work i.e. issued uops that eventually get retired. Ideally; all pipeline slots would be attributed to the Retiring category. Retiring of 100% would indicate the maximum Pipeline_Width throughput was achieved. Maximizing Retiring typically increases the Instructions-per-cycle (see tma_info_thread_ipc metric). Note that a high Retiring value does not necessary mean there is no room for more performance. For example; Heavy-operations or Microcode Assists are categorized under Retiring. They often indicate suboptimal performance and can often be optimized or avoided. ", + "BriefDescription": "This category represents fraction of slots utilized by useful work i.e. issued uops that eventually get retired. Ideally; all pipeline slots would be attributed to the Retiring category. Retiring of 100% would indicate the maximum Pipeline_Width throughput was achieved. Maximizing Retiring typically increases the Instructions-per-cycle (see IPC metric). Note that a high Retiring value does not necessary mean there is no room for more performance. For example; Heavy-operations or Microcode Assists are categorized under Retiring. They often indicate suboptimal performance and can often be optimized or avoided. ", "UnitOfMeasure": "percent", "Events": [ { diff --git a/SPR/metrics/perf/sapphirerapids_metrics_perf.json b/SPR/metrics/perf/sapphirerapids_metrics_perf.json index 2100a6c9..17a3d740 100644 --- a/SPR/metrics/perf/sapphirerapids_metrics_perf.json +++ b/SPR/metrics/perf/sapphirerapids_metrics_perf.json @@ -1289,7 +1289,7 @@ "MetricName": "tma_retiring", "ScaleUnit": "100%", "MetricThreshold": "tma_retiring > 0.7 | tma_heavy_operations > 0.1", - "PublicDescription": "This category represents fraction of slots utilized by useful work i.e. issued uops that eventually get retired. Ideally; all pipeline slots would be attributed to the Retiring category. Retiring of 100% would indicate the maximum Pipeline_Width throughput was achieved. Maximizing Retiring typically increases the Instructions-per-cycle (see tma_info_thread_ipc metric). Note that a high Retiring value does not necessary mean there is no room for more performance. For example; Heavy-operations or Microcode Assists are categorized under Retiring. They often indicate suboptimal performance and can often be optimized or avoided. Sample with: UOPS_RETIRED.SLOTS.", + "PublicDescription": "This category represents fraction of slots utilized by useful work i.e. issued uops that eventually get retired. Ideally; all pipeline slots would be attributed to the Retiring category. Retiring of 100% would indicate the maximum Pipeline_Width throughput was achieved. Maximizing Retiring typically increases the Instructions-per-cycle (see IPC metric). Note that a high Retiring value does not necessary mean there is no room for more performance. For example; Heavy-operations or Microcode Assists are categorized under Retiring. They often indicate suboptimal performance and can often be optimized or avoided. Sample with: UOPS_RETIRED.SLOTS.", "DefaultMetricgroupName": "TopdownL1", "MetricGroupnoGroup": "TopdownL1;Default" }, diff --git a/SPR/metrics/perf/sapphirerapidshbm_metrics_perf.json b/SPR/metrics/perf/sapphirerapidshbm_metrics_perf.json index 7525a96d..45216c93 100644 --- a/SPR/metrics/perf/sapphirerapidshbm_metrics_perf.json +++ b/SPR/metrics/perf/sapphirerapidshbm_metrics_perf.json @@ -1297,7 +1297,7 @@ "MetricName": "tma_retiring", "ScaleUnit": "100%", "MetricThreshold": "tma_retiring > 0.7 | tma_heavy_operations > 0.1", - "PublicDescription": "This category represents fraction of slots utilized by useful work i.e. issued uops that eventually get retired. Ideally; all pipeline slots would be attributed to the Retiring category. Retiring of 100% would indicate the maximum Pipeline_Width throughput was achieved. Maximizing Retiring typically increases the Instructions-per-cycle (see tma_info_thread_ipc metric). Note that a high Retiring value does not necessary mean there is no room for more performance. For example; Heavy-operations or Microcode Assists are categorized under Retiring. They often indicate suboptimal performance and can often be optimized or avoided. Sample with: UOPS_RETIRED.SLOTS.", + "PublicDescription": "This category represents fraction of slots utilized by useful work i.e. issued uops that eventually get retired. Ideally; all pipeline slots would be attributed to the Retiring category. Retiring of 100% would indicate the maximum Pipeline_Width throughput was achieved. Maximizing Retiring typically increases the Instructions-per-cycle (see IPC metric). Note that a high Retiring value does not necessary mean there is no room for more performance. For example; Heavy-operations or Microcode Assists are categorized under Retiring. They often indicate suboptimal performance and can often be optimized or avoided. Sample with: UOPS_RETIRED.SLOTS.", "DefaultMetricgroupName": "TopdownL1", "MetricGroupnoGroup": "TopdownL1;Default" }, diff --git a/SPR/metrics/sapphirerapids_metrics.json b/SPR/metrics/sapphirerapids_metrics.json index 379e2127..6f4790f1 100644 --- a/SPR/metrics/sapphirerapids_metrics.json +++ b/SPR/metrics/sapphirerapids_metrics.json @@ -8402,7 +8402,7 @@ "MetricName": "Retiring", "LegacyName": "metric_TMA_Retiring(%)", "Level": 1, - "BriefDescription": "This category represents fraction of slots utilized by useful work i.e. issued uops that eventually get retired. Ideally; all pipeline slots would be attributed to the Retiring category. Retiring of 100% would indicate the maximum Pipeline_Width throughput was achieved. Maximizing Retiring typically increases the Instructions-per-cycle (see tma_info_thread_ipc metric). Note that a high Retiring value does not necessary mean there is no room for more performance. For example; Heavy-operations or Microcode Assists are categorized under Retiring. They often indicate suboptimal performance and can often be optimized or avoided. ", + "BriefDescription": "This category represents fraction of slots utilized by useful work i.e. issued uops that eventually get retired. Ideally; all pipeline slots would be attributed to the Retiring category. Retiring of 100% would indicate the maximum Pipeline_Width throughput was achieved. Maximizing Retiring typically increases the Instructions-per-cycle (see IPC metric). Note that a high Retiring value does not necessary mean there is no room for more performance. For example; Heavy-operations or Microcode Assists are categorized under Retiring. They often indicate suboptimal performance and can often be optimized or avoided. ", "UnitOfMeasure": "percent", "Events": [ { diff --git a/SPR/metrics/sapphirerapidshbm_metrics.json b/SPR/metrics/sapphirerapidshbm_metrics.json index 54509922..48e3fab1 100644 --- a/SPR/metrics/sapphirerapidshbm_metrics.json +++ b/SPR/metrics/sapphirerapidshbm_metrics.json @@ -8502,7 +8502,7 @@ "MetricName": "Retiring", "LegacyName": "metric_TMA_Retiring(%)", "Level": 1, - "BriefDescription": "This category represents fraction of slots utilized by useful work i.e. issued uops that eventually get retired. Ideally; all pipeline slots would be attributed to the Retiring category. Retiring of 100% would indicate the maximum Pipeline_Width throughput was achieved. Maximizing Retiring typically increases the Instructions-per-cycle (see tma_info_thread_ipc metric). Note that a high Retiring value does not necessary mean there is no room for more performance. For example; Heavy-operations or Microcode Assists are categorized under Retiring. They often indicate suboptimal performance and can often be optimized or avoided. ", + "BriefDescription": "This category represents fraction of slots utilized by useful work i.e. issued uops that eventually get retired. Ideally; all pipeline slots would be attributed to the Retiring category. Retiring of 100% would indicate the maximum Pipeline_Width throughput was achieved. Maximizing Retiring typically increases the Instructions-per-cycle (see IPC metric). Note that a high Retiring value does not necessary mean there is no room for more performance. For example; Heavy-operations or Microcode Assists are categorized under Retiring. They often indicate suboptimal performance and can often be optimized or avoided. ", "UnitOfMeasure": "percent", "Events": [ { diff --git a/TGL/metrics/perf/tigerlake_metrics_perf.json b/TGL/metrics/perf/tigerlake_metrics_perf.json index ac7f50fd..c353e762 100644 --- a/TGL/metrics/perf/tigerlake_metrics_perf.json +++ b/TGL/metrics/perf/tigerlake_metrics_perf.json @@ -868,7 +868,7 @@ "MetricName": "tma_retiring", "ScaleUnit": "100%", "MetricThreshold": "tma_retiring > 0.7 | tma_heavy_operations > 0.1", - "PublicDescription": "This category represents fraction of slots utilized by useful work i.e. issued uops that eventually get retired. Ideally; all pipeline slots would be attributed to the Retiring category. Retiring of 100% would indicate the maximum Pipeline_Width throughput was achieved. Maximizing Retiring typically increases the Instructions-per-cycle (see tma_info_thread_ipc metric). Note that a high Retiring value does not necessary mean there is no room for more performance. For example; Heavy-operations or Microcode Assists are categorized under Retiring. They often indicate suboptimal performance and can often be optimized or avoided. Sample with: UOPS_RETIRED.SLOTS.", + "PublicDescription": "This category represents fraction of slots utilized by useful work i.e. issued uops that eventually get retired. Ideally; all pipeline slots would be attributed to the Retiring category. Retiring of 100% would indicate the maximum Pipeline_Width throughput was achieved. Maximizing Retiring typically increases the Instructions-per-cycle (see IPC metric). Note that a high Retiring value does not necessary mean there is no room for more performance. For example; Heavy-operations or Microcode Assists are categorized under Retiring. They often indicate suboptimal performance and can often be optimized or avoided. Sample with: UOPS_RETIRED.SLOTS.", "DefaultMetricgroupName": "TopdownL1", "MetricGroupnoGroup": "TopdownL1;Default" }, diff --git a/TGL/metrics/tigerlake_metrics.json b/TGL/metrics/tigerlake_metrics.json index 8d3736d4..de805cb1 100644 --- a/TGL/metrics/tigerlake_metrics.json +++ b/TGL/metrics/tigerlake_metrics.json @@ -6950,7 +6950,7 @@ "MetricName": "Retiring", "LegacyName": "metric_TMA_Retiring(%)", "Level": 1, - "BriefDescription": "This category represents fraction of slots utilized by useful work i.e. issued uops that eventually get retired. Ideally; all pipeline slots would be attributed to the Retiring category. Retiring of 100% would indicate the maximum Pipeline_Width throughput was achieved. Maximizing Retiring typically increases the Instructions-per-cycle (see tma_info_thread_ipc metric). Note that a high Retiring value does not necessary mean there is no room for more performance. For example; Heavy-operations or Microcode Assists are categorized under Retiring. They often indicate suboptimal performance and can often be optimized or avoided. ", + "BriefDescription": "This category represents fraction of slots utilized by useful work i.e. issued uops that eventually get retired. Ideally; all pipeline slots would be attributed to the Retiring category. Retiring of 100% would indicate the maximum Pipeline_Width throughput was achieved. Maximizing Retiring typically increases the Instructions-per-cycle (see IPC metric). Note that a high Retiring value does not necessary mean there is no room for more performance. For example; Heavy-operations or Microcode Assists are categorized under Retiring. They often indicate suboptimal performance and can often be optimized or avoided. ", "UnitOfMeasure": "percent", "Events": [ {