# Read Code Optimizations memory percentages against trace allocations

> What is the denominator of a Code Optimizations memory percentage?

- Canonical URL: https://update.dsesecurity.com/updates/dse-20260909-121-read-code-optimizations-memory-percentages-against-trace-allocations/
- Publisher: Detection Systems & Engineering (DSE Security)
- Author: DSE Security Editorial Team
- Published: 2026-09-10T00:29:55+00:00
- Modified: 2026-09-10T00:52:38+00:00
- Last reviewed by DSE: 2026-09-09
- Resource type: Explainer
- DSE priority: Information
- Topics: IT
- Reading time: 2 minutes

## What you need to know

What is the denominator of a Code Optimizations memory percentage?

## Potentially affected

Application Insights Code Optimizations memory findings viewed for an individual resource.

## DSE recommendation

Describe a memory finding as its share of allocations in the trace, and retain allocation bytes and type details beside that percentage.

## Article

## Source facts

Code Optimizations expresses a memory finding as a percentage of all allocations in the trace. It also provides actual allocation sizes in bytes and a breakdown of allocated types within the call. The individual-resource view can filter results by time, role and insight type, and an insight includes its call stack. [Microsoft Learn](https://learn.microsoft.com/en-us/azure/azure-monitor/optimization-insights/view-code-optimizations).

## Applicability

Use this interpretation for a Code Optimizations memory insight, not as a replacement for a separately measured host-memory or process-residency value. Keep the trace and selected workload context attached to the number.

## DSE recommendation

Describe a memory finding as its share of allocations in the trace, and retain allocation bytes and type details beside that percentage. Ask the application owner to identify the relevant call path and whether the observed workload represents the problem being investigated. Do not translate an allocation share directly into a claim that the method occupies that percentage of the machine’s RAM. Separate the diagnostic lead from any proposed code change.

## Verification

Open the insight with an explicit time and role selection and inspect its allocation details and call stack. Compare like-for-like observations when evaluating a proposed change, recording any workload or capture differences. Check that the resulting ticket or report names the allocation denominator rather than using an ambiguous memory percentage. Retain the underlying observations; a lower share alone should not be reported as a measured reduction in resident memory or as proof that the application’s problem was resolved.

## Official references

[Microsoft Learn: Interpret Code Optimizations results](https://learn.microsoft.com/en-us/azure/azure-monitor/optimization-insights/view-code-optimizations). Source reviewed September 9, 2026.

## Primary reference

- Name: Access and Interpret Code Optimizations Results - Azure Monitor | Microsoft Learn
- Authority: Microsoft Learn
- URL: https://learn.microsoft.com/en-us/azure/azure-monitor/optimization-insights/view-code-optimizations
- Source publication date: Not stated by the source

## Citation and use

Preferred citation: “Read Code Optimizations memory percentages against trace allocations,” DSE Security, https://update.dsesecurity.com/updates/dse-20260909-121-read-code-optimizations-memory-percentages-against-trace-allocations/
Publishing principles: https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/
Usage and citation policy: https://update.dsesecurity.com/usage/
Copyright © 2026 Detection Systems & Engineering. All rights reserved.