Memory usage is too high for large tenant
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 30/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- azure, kubernetes, powershell
- Domain
- devops, performance
Research direction
Start with AzGovVizParallel.ps1 and reproduce the reported command using the large-tenant options, memory reporting, and the supplied environment variables. Compare memory around subscription processing and TenantSummary RoleAssignments processing. Done means the 115-subscription, 39,558-role-assignment workload no longer grows until it is OOMKilled.
Written by the indexing model from the issue text.
Description
AzGovViz version
6.7.2
CodeRunPlatform
Jenkins, on AKS, with azure-powershell runner image, version: '15.0.0-alpine-3.22'.
limitMemory:'12Gi', requestMemory:'3Gi', limitCpu:'2.5'
Describe the bug
Script memory usage is growing continuously, without important memory release, and finish by a OOMKilled, because it is using all the memory.
Despite a aggressive garbage collection settings.
First memory ramp end with "CustomDataCollection Subscriptions processing" end (16:59).
A secund memory ramp end after "processing (pre) TenantSummary RoleAssignments" (17:17).
Screenshots
Additional context
Command line :
pwsh/AzGovVizParallel.ps1 -ManagementGroupId 'myMainMG' -OutputPath 'AzGovViz-Output' -HierarchyMapOnly -NoPIMEligibility -ShowMemoryUsage -LargeTenant -DoTranscript -CriticalMemoryUsage 70
Environment vars :
DOTNET_GCHeapHardLimitPercent=0x63
DOTNET_GCHeapCount=4
Landing zone insights :
- 54 relevant Management Groups
- 115 relevant Subscriptions
- RoleAssignments (all 39558)
- Dominant language
- PowerShell
- Stars
- 185
- Forks
- 72
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from Azure/Azure-Governance-Visualizer
-
Difficulty 3/5 1-2 days Newbie friendliness 55/100
Azure/Azure-Governance-Visualizer#70 · 4 comments · 2 reactions ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 55/100
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
-
Import Failed Open
Difficulty 4/5 3-5 days Newbie friendliness 25/100
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
Azure/Azure-Governance-Visualizer#62 · 1 comment ·
All issues in Azure/Azure-Governance-Visualizer
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 84/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
danielmiessler/LifeOS#2215 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
sympozium-ai/sympozium#627 ·
-
repo:raw-data
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
hotosm/raw-data-api#316 · 1 comment ·
-
agentic-workflows cascade-suspected
Difficulty 2/5 1-3 hours Newbie friendliness 68/100